Typo: ebs.csi.aws.com instead of aws.ebs.csi.driver

Per driver [code](966da33cff/pkg/driver/driver.go (L49C30-L49C45))

Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>

design/Implemented/handle-backup-of-volumes-by-resources-filters.md

@@ -86,7 +86,7 @@ volumePolicies:
     # capacity condition matches the volumes whose capacity falls into the range
     capacity: "0,100Gi"
     csi:
-      driver: aws.ebs.csi.driver
+      driver: ebs.csi.aws.com
       fsType: ext4
     storageClass:
     - gp2
@@ -174,7 +174,7 @@ data:
   - conditions:
       capacity: "0,100Gi"
       csi:
-        driver: aws.ebs.csi.driver
+        driver: ebs.csi.aws.com
         fsType: ext4
       storageClass:
       - gp2

internal/resourcepolicies/resource_policies_test.go

@@ -276,7 +276,7 @@ volumePolicies:
 			vol: &v1.PersistentVolume{
 				Spec: v1.PersistentVolumeSpec{
 					PersistentVolumeSource: v1.PersistentVolumeSource{
-						CSI: &v1.CSIPersistentVolumeSource{Driver: "aws.ebs.csi.driver"},
+						CSI: &v1.CSIPersistentVolumeSource{Driver: "ebs.csi.aws.com"},
 					}},
 			},
 			skip: true,
@@ -311,7 +311,7 @@ volumePolicies:
 						v1.ResourceStorage: resource.MustParse("1Gi"),
 					},
 					PersistentVolumeSource: v1.PersistentVolumeSource{
-						CSI: &v1.CSIPersistentVolumeSource{Driver: "aws.ebs.csi.driver"},
+						CSI: &v1.CSIPersistentVolumeSource{Driver: "ebs.csi.aws.com"},
 					}},
 			},
 			skip: true,

site/content/docs/main/resource-filtering.md

@@ -264,7 +264,7 @@ The policies YAML config file would look like this:
         capacity: "10,100Gi"
         # pv matches specific csi driver
         csi:
-          driver: aws.ebs.csi.driver
+          driver: ebs.csi.aws.com
         # pv matches one of the storage class list
         storageClass:
           - gp2

site/content/docs/v1.11/resource-filtering.md

@@ -241,7 +241,7 @@ Velero only support volume resource policies currently, other kinds of resource
         capacity: "10,100Gi"
         # pv matches specific csi driver
         csi:
-          driver: aws.ebs.csi.driver
+          driver: ebs.csi.aws.com
         # pv matches one of the storage class list
         storageClass:
         - gp2

site/content/docs/v1.12/resource-filtering.md

@@ -241,7 +241,7 @@ Velero only support volume resource policies currently, other kinds of resource
         capacity: "10,100Gi"
         # pv matches specific csi driver
         csi:
-          driver: aws.ebs.csi.driver
+          driver: ebs.csi.aws.com
         # pv matches one of the storage class list
         storageClass:
         - gp2

site/content/docs/v1.13/resource-filtering.md

@@ -259,7 +259,7 @@ Velero only support volume resource policies currently, other kinds of resource
         capacity: "10,100Gi"
         # pv matches specific csi driver
         csi:
-          driver: aws.ebs.csi.driver
+          driver: ebs.csi.aws.com
         # pv matches one of the storage class list
         storageClass:
           - gp2

site/content/docs/v1.14/resource-filtering.md

@@ -264,7 +264,7 @@ The policies YAML config file would look like this:
         capacity: "10,100Gi"
         # pv matches specific csi driver
         csi:
-          driver: aws.ebs.csi.driver
+          driver: ebs.csi.aws.com
         # pv matches one of the storage class list
         storageClass:
           - gp2

site/content/docs/v1.15/resource-filtering.md

@@ -264,7 +264,7 @@ The policies YAML config file would look like this:
         capacity: "10,100Gi"
         # pv matches specific csi driver
         csi:
-          driver: aws.ebs.csi.driver
+          driver: ebs.csi.aws.com
         # pv matches one of the storage class list
         storageClass:
           - gp2