feat(storagetransfer): update the API

#### storagetransfer:v1 The following keys were added: - schemas.LoggingConfig.properties.logActionStates.description - schemas.LoggingConfig.properties.logActionStates.items.enum - schemas.LoggingConfig.properties.logActionStates.items.enumDescriptions - schemas.LoggingConfig.properties.logActionStates.items.type - schemas.LoggingConfig.properties.logActionStates.type - schemas.LoggingConfig.properties.logActions.description - schemas.LoggingConfig.properties.logActions.items.enum - schemas.LoggingConfig.properties.logActions.items.enumDescriptions - schemas.LoggingConfig.properties.logActions.items.type - schemas.LoggingConfig.properties.logActions.type - schemas.TransferManifest.description - schemas.TransferManifest.id - schemas.TransferManifest.properties.location.description - schemas.TransferManifest.properties.location.type - schemas.TransferManifest.type - schemas.TransferSpec.properties.transferManifest.$ref - schemas.TransferSpec.properties.transferManifest.description
googleapis · Nov 25, 2021 · d4017b9 · d4017b9
1 parent 3687772
commit d4017b9
Show file tree

Hide file tree

Showing 2 changed files with 73 additions and 1 deletion.
diff --git a/discovery/storagetransfer-v1.json b/discovery/storagetransfer-v1.json
@@ -600,7 +600,7 @@
       }
     }
   },
-  "revision": "20211105",
+  "revision": "20211111",
   "rootUrl": "https://storagetransfer.googleapis.com/",
   "schemas": {
     "AgentPool": {
@@ -938,6 +938,42 @@
         "enableOnpremGcsTransferLogs": {
           "description": "Enables the Cloud Storage transfer logs for this transfer. This is only supported for transfer jobs with PosixFilesystem sources. The default is that logs are not generated for this transfer.",
           "type": "boolean"
+        },
+        "logActionStates": {
+          "description": "States in which `log_actions` are logged. If empty, no logs are generated. This is not yet supported for transfers with PosixFilesystem data sources.",
+          "items": {
+            "enum": [
+              "LOGGABLE_ACTION_STATE_UNSPECIFIED",
+              "SUCCEEDED",
+              "FAILED"
+            ],
+            "enumDescriptions": [
+              "Default value. This value is unused.",
+              "`LoggableAction` is completed successfully. `SUCCEEDED` actions are logged as INFO.",
+              "`LoggableAction` is terminated in an error state. `FAILED` actions are logged as ERROR."
+            ],
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "logActions": {
+          "description": "Actions to be logged. If empty, no logs are generated. This is not yet supported for transfers with PosixFilesystem data sources.",
+          "items": {
+            "enum": [
+              "LOGGABLE_ACTION_UNSPECIFIED",
+              "FIND",
+              "DELETE",
+              "COPY"
+            ],
+            "enumDescriptions": [
+              "Default value. This value is unused.",
+              "Finding objects to transfer e.g. listing objects of the source bucket.",
+              "Deleting objects at source or destination.",
+              "Copying objects from source to destination."
+            ],
+            "type": "string"
+          },
+          "type": "array"
         }
       },
       "type": "object"
@@ -1363,6 +1399,17 @@
       },
       "type": "object"
     },
+    "TransferManifest": {
+      "description": "Specifies where the manifest is located.",
+      "id": "TransferManifest",
+      "properties": {
+        "location": {
+          "description": "Holds URI-encoded path to find the manifest. It can be located in data_source, data_sink, or separately in GCS. For data_source and data_sink, the manifest location is relative to the path specified by that data_source or data_sink. If manifest is in GCS, use format \"gs:///\". If manifest is in data_source, use format \"source://\". If manifest is in data_sink, use format \"sink://\".",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "TransferOperation": {
       "description": "A description of the execution of a transfer.",
       "id": "TransferOperation",
@@ -1496,6 +1543,10 @@
           "description": "Specifies the agent pool name associated with the posix data source. When unspecified, the default name is used.",
           "type": "string"
         },
+        "transferManifest": {
+          "$ref": "TransferManifest",
+          "description": "A manifest file provides a list of objects to be transferred from the data source. This field points to the location of the manifest file. Otherwise, the entire source bucket is used. ObjectConditions still apply."
+        },
         "transferOptions": {
           "$ref": "TransferOptions",
           "description": "If the option delete_objects_unique_in_sink is `true` and time-based object conditions such as 'last modification time' are specified, the request fails with an INVALID_ARGUMENT error."

diff --git a/src/apis/storagetransfer/v1.ts b/src/apis/storagetransfer/v1.ts
@@ -364,6 +364,14 @@ export namespace storagetransfer_v1 {
      * Enables the Cloud Storage transfer logs for this transfer. This is only supported for transfer jobs with PosixFilesystem sources. The default is that logs are not generated for this transfer.
      */
     enableOnpremGcsTransferLogs?: boolean | null;
+    /**
+     * Actions to be logged. If empty, no logs are generated. This is not yet supported for transfers with PosixFilesystem data sources.
+     */
+    logActions?: string[] | null;
+    /**
+     * States in which `log_actions` are logged. If empty, no logs are generated. This is not yet supported for transfers with PosixFilesystem data sources.
+     */
+    logActionStates?: string[] | null;
   }
   /**
    * Specification to configure notifications published to Pub/Sub. Notifications are published to the customer-provided topic using the following `PubsubMessage.attributes`: * `"eventType"`: one of the EventType values * `"payloadFormat"`: one of the PayloadFormat values * `"projectId"`: the project_id of the `TransferOperation` * `"transferJobName"`: the transfer_job_name of the `TransferOperation` * `"transferOperationName"`: the name of the `TransferOperation` The `PubsubMessage.data` contains a TransferOperation resource formatted according to the specified `PayloadFormat`.
@@ -667,6 +675,15 @@ export namespace storagetransfer_v1 {
      */
     transferSpec?: Schema$TransferSpec;
   }
+  /**
+   * Specifies where the manifest is located.
+   */
+  export interface Schema$TransferManifest {
+    /**
+     * Holds URI-encoded path to find the manifest. It can be located in data_source, data_sink, or separately in GCS. For data_source and data_sink, the manifest location is relative to the path specified by that data_source or data_sink. If manifest is in GCS, use format "gs:///". If manifest is in data_source, use format "source://". If manifest is in data_sink, use format "sink://".
+     */
+    location?: string | null;
+  }
   /**
    * A description of the execution of a transfer.
    */
@@ -773,6 +790,10 @@ export namespace storagetransfer_v1 {
      * Specifies the agent pool name associated with the posix data source. When unspecified, the default name is used.
      */
     sourceAgentPoolName?: string | null;
+    /**
+     * A manifest file provides a list of objects to be transferred from the data source. This field points to the location of the manifest file. Otherwise, the entire source bucket is used. ObjectConditions still apply.
+     */
+    transferManifest?: Schema$TransferManifest;
     /**
      * If the option delete_objects_unique_in_sink is `true` and time-based object conditions such as 'last modification time' are specified, the request fails with an INVALID_ARGUMENT error.
      */