feat(storage): update the api

#### storage:v1

The following keys were added:
- schemas.Bucket.properties.customPlacementConfig (Total Keys: 3)

Author: yoshi-automation

docs/dyn/storage_v1.buckets.html

@@ -196,6 +196,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -253,7 +258,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -425,6 +430,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -482,7 +492,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -615,6 +625,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -672,7 +687,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -802,6 +817,11 @@ <h3>Method Details</h3>
           ],
         },
       ],
+      &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+        &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+          &quot;A String&quot;,
+        ],
+      },
       &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
       &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
         { # An access-control entry.
@@ -859,7 +879,7 @@ <h3>Method Details</h3>
           {
             &quot;action&quot;: { # The action to take.
               &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-              &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+              &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
             },
             &quot;condition&quot;: { # The condition(s) under which the action will be taken.
               &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -999,6 +1019,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -1056,7 +1081,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -1175,6 +1200,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -1232,7 +1262,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -1367,6 +1397,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -1424,7 +1459,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -1672,6 +1707,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -1729,7 +1769,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.
@@ -1864,6 +1904,11 @@ <h3>Method Details</h3>
       ],
     },
   ],
+  &quot;customPlacementConfig&quot;: { # The bucket&#x27;s custom placement configuration for Custom Dual Regions.
+    &quot;dataLocations&quot;: [ # The list of regional locations in which data is placed.
+      &quot;A String&quot;,
+    ],
+  },
   &quot;defaultEventBasedHold&quot;: True or False, # The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold&#x27;s release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.
   &quot;defaultObjectAcl&quot;: [ # Default access controls to apply to new objects when no ACL is provided.
     { # An access-control entry.
@@ -1921,7 +1966,7 @@ <h3>Method Details</h3>
       {
         &quot;action&quot;: { # The action to take.
           &quot;storageClass&quot;: &quot;A String&quot;, # Target storage class. Required iff the type of the action is SetStorageClass.
-          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete and SetStorageClass are supported.
+          &quot;type&quot;: &quot;A String&quot;, # Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.
         },
         &quot;condition&quot;: { # The condition(s) under which the action will be taken.
           &quot;age&quot;: 42, # Age of an object (in days). This condition is satisfied when an object reaches the specified age.