chore(bigquerydatatransfer): update the api

#### bigquerydatatransfer:v1

The following keys were changed:
- documentationLink (Total Keys: 1)
- resources.projects.resources.locations.resources.transferConfigs.methods.patch.parameters.name (Total Keys: 1)
- resources.projects.resources.locations.resources.transferConfigs.resources.runs.methods.list.parameters.states (Total Keys: 1)
- resources.projects.resources.transferConfigs.methods.patch.parameters.name (Total Keys: 1)
- resources.projects.resources.transferConfigs.resources.runs.methods.list.parameters.states (Total Keys: 1)
- revision (Total Keys: 1)
- schemas.TransferConfig.properties.name (Total Keys: 1)
- schemas.TransferConfig.properties.state (Total Keys: 1)
- schemas.TransferRun.properties.state (Total Keys: 1)

Author: yoshi-automation

docs/dyn/bigquerydatatransfer_v1.projects.locations.transferConfigs.html

@@ -131,7 +131,7 @@ <h3>Method Details</h3>
   &quot;emailPreferences&quot;: { # Represents preferences for sending email notifications for transfer run events. # Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config.
     &quot;enableFailureEmail&quot;: True or False, # If true, email notifications will be sent on transfer run failures.
   },
-  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form of `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. The name is automatically generated based on the config_id specified in CreateTransferConfigRequest along with project_id and region. If config_id is not provided, usually a uuid, even though it is not guaranteed or required, will be generated for config_id.
+  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config.
   &quot;nextRunTime&quot;: &quot;A String&quot;, # Output only. Next time when data transfer will run.
   &quot;notificationPubsubTopic&quot;: &quot;A String&quot;, # Pub/Sub topic where notifications will be sent after transfer runs associated with this transfer config finish.
   &quot;params&quot;: { # Data transfer specific parameters.
@@ -169,7 +169,7 @@ <h3>Method Details</h3>
   &quot;emailPreferences&quot;: { # Represents preferences for sending email notifications for transfer run events. # Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config.
     &quot;enableFailureEmail&quot;: True or False, # If true, email notifications will be sent on transfer run failures.
   },
-  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form of `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. The name is automatically generated based on the config_id specified in CreateTransferConfigRequest along with project_id and region. If config_id is not provided, usually a uuid, even though it is not guaranteed or required, will be generated for config_id.
+  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config.
   &quot;nextRunTime&quot;: &quot;A String&quot;, # Output only. Next time when data transfer will run.
   &quot;notificationPubsubTopic&quot;: &quot;A String&quot;, # Pub/Sub topic where notifications will be sent after transfer runs associated with this transfer config finish.
   &quot;params&quot;: { # Data transfer specific parameters.
@@ -229,7 +229,7 @@ <h3>Method Details</h3>
   &quot;emailPreferences&quot;: { # Represents preferences for sending email notifications for transfer run events. # Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config.
     &quot;enableFailureEmail&quot;: True or False, # If true, email notifications will be sent on transfer run failures.
   },
-  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form of `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. The name is automatically generated based on the config_id specified in CreateTransferConfigRequest along with project_id and region. If config_id is not provided, usually a uuid, even though it is not guaranteed or required, will be generated for config_id.
+  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config.
   &quot;nextRunTime&quot;: &quot;A String&quot;, # Output only. Next time when data transfer will run.
   &quot;notificationPubsubTopic&quot;: &quot;A String&quot;, # Pub/Sub topic where notifications will be sent after transfer runs associated with this transfer config finish.
   &quot;params&quot;: { # Data transfer specific parameters.
@@ -277,7 +277,7 @@ <h3>Method Details</h3>
       &quot;emailPreferences&quot;: { # Represents preferences for sending email notifications for transfer run events. # Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config.
         &quot;enableFailureEmail&quot;: True or False, # If true, email notifications will be sent on transfer run failures.
       },
-      &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form of `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. The name is automatically generated based on the config_id specified in CreateTransferConfigRequest along with project_id and region. If config_id is not provided, usually a uuid, even though it is not guaranteed or required, will be generated for config_id.
+      &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config.
       &quot;nextRunTime&quot;: &quot;A String&quot;, # Output only. Next time when data transfer will run.
       &quot;notificationPubsubTopic&quot;: &quot;A String&quot;, # Pub/Sub topic where notifications will be sent after transfer runs associated with this transfer config finish.
       &quot;params&quot;: { # Data transfer specific parameters.
@@ -316,7 +316,7 @@ <h3>Method Details</h3>
   <pre>Updates a data transfer configuration. All fields must be set, even if they are not updated.
 
 Args:
-  name: string, The resource name of the transfer config. Transfer config names have the form of `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. The name is automatically generated based on the config_id specified in CreateTransferConfigRequest along with project_id and region. If config_id is not provided, usually a uuid, even though it is not guaranteed or required, will be generated for config_id. (required)
+  name: string, The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config. (required)
   body: object, The request body.
     The object takes the form of:
 
@@ -330,7 +330,7 @@ <h3>Method Details</h3>
   &quot;emailPreferences&quot;: { # Represents preferences for sending email notifications for transfer run events. # Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config.
     &quot;enableFailureEmail&quot;: True or False, # If true, email notifications will be sent on transfer run failures.
   },
-  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form of `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. The name is automatically generated based on the config_id specified in CreateTransferConfigRequest along with project_id and region. If config_id is not provided, usually a uuid, even though it is not guaranteed or required, will be generated for config_id.
+  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config.
   &quot;nextRunTime&quot;: &quot;A String&quot;, # Output only. Next time when data transfer will run.
   &quot;notificationPubsubTopic&quot;: &quot;A String&quot;, # Pub/Sub topic where notifications will be sent after transfer runs associated with this transfer config finish.
   &quot;params&quot;: { # Data transfer specific parameters.
@@ -369,7 +369,7 @@ <h3>Method Details</h3>
   &quot;emailPreferences&quot;: { # Represents preferences for sending email notifications for transfer run events. # Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config.
     &quot;enableFailureEmail&quot;: True or False, # If true, email notifications will be sent on transfer run failures.
   },
-  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form of `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. The name is automatically generated based on the config_id specified in CreateTransferConfigRequest along with project_id and region. If config_id is not provided, usually a uuid, even though it is not guaranteed or required, will be generated for config_id.
+  &quot;name&quot;: &quot;A String&quot;, # The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/locations/{region}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config.
   &quot;nextRunTime&quot;: &quot;A String&quot;, # Output only. Next time when data transfer will run.
   &quot;notificationPubsubTopic&quot;: &quot;A String&quot;, # Pub/Sub topic where notifications will be sent after transfer runs associated with this transfer config finish.
   &quot;params&quot;: { # Data transfer specific parameters.

docs/dyn/bigquerydatatransfer_v1.projects.locations.transferConfigs.runs.html

@@ -177,12 +177,12 @@ <h3>Method Details</h3>
       LATEST - Only latest run per day should be returned.
   states: string, When specified, only transfer runs with requested states are returned. (repeated)
     Allowed values
-      TRANSFER_STATE_UNSPECIFIED - State placeholder.
-      PENDING - Data transfer is scheduled and is waiting to be picked up by data transfer backend.
-      RUNNING - Data transfer is in progress.
-      SUCCEEDED - Data transfer completed successfully.
-      FAILED - Data transfer failed.
-      CANCELLED - Data transfer is cancelled.
+      TRANSFER_STATE_UNSPECIFIED - State placeholder (0).
+      PENDING - Data transfer is scheduled and is waiting to be picked up by data transfer backend (2).
+      RUNNING - Data transfer is in progress (3).
+      SUCCEEDED - Data transfer completed successfully (4).
+      FAILED - Data transfer failed (5).
+      CANCELLED - Data transfer is cancelled (6).
   x__xgafv: string, V1 error format.
     Allowed values
       1 - v1 error format