Method: projects.locations.assets.batchUpdate

Updates the parameters of a list of assets.

HTTP request

POST https://migrationcenter.googleapis.com/v1/{parent=projects/*/locations/*}/assets:batchUpdate

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
parent

string

Required. Parent value for batch asset update.

Request body

The request body contains data with the following structure:

JSON representation 
{
  "requests": [
    {
      object (UpdateAssetRequest)
    }
  ]
}
Fields
requests[]

object (UpdateAssetRequest)

Required. The request message specifying the resources to update. A maximum of 1000 assets can be modified in a batch.

Response body

Response for updating a list of assets.

If successful, the response body contains data with the following structure:

JSON representation 
{
  "assets": [
    {
      object (Asset)
    }
  ]
}
Fields
assets[]

object (Asset)

Update asset content. The content only includes values after field mask being applied.

Authorization scopes

Requires the following OAuth scope:

  • https://www.googleapis.com/auth/cloud-platform

For more information, see the Authentication Overview.

UpdateAssetRequest

A request to update an asset.

JSON representation 
{
  "updateMask": string,
  "asset": {
    object (Asset)
  },
  "requestId": string
}
Fields
updateMask

string (FieldMask format)

Required. Field mask is used to specify the fields to be overwritten in the Asset resource by the update. The values specified in the updateMask field are relative to the resource, not the full request. A field will be overwritten if it is in the mask. A single * value in the mask lets you to overwrite all fields.

This is a comma-separated list of fully qualified names of fields. Example: "user.displayName,photo".
asset

object (Asset)

Required. The resource being updated.
requestId

string

Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request.

For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.

The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).