ModernizationTestingResourcesBatchInsertRequest

JSON representation

JSON representation

JSON representation
{ "project": string, "resourceCount": string, "resourceNamePrefix": string, "description": string, "batchPayload": { object (`BatchPayload`) }, "insertRequests": [ { object (`IndividualInsertModernizationTestingResourceRequest`) } ], "minResourceCount": string, "errorRules": { string: integer, ... }, "requestId": string }

{
  "project": string,
  "resourceCount": string,
  "resourceNamePrefix": string,
  "description": string,
  "batchPayload": {
    object (BatchPayload)
  },
  "insertRequests": [
    {
      object (IndividualInsertModernizationTestingResourceRequest)
    }
  ],
  "minResourceCount": string,
  "errorRules": {
    string: integer,
    ...
  },
  "requestId": string
}

Fields
`project`	`string` Project ID for this request.
`resourceCount`	`string (int64 format)`
`resourceNamePrefix`	`string`
`description`	`string`
`batchPayload`	`object (BatchPayload)`
`insertRequests[]`	`object (IndividualInsertModernizationTestingResourceRequest)` Contains the individual insert requests only when ExtractTargets is not specified in the BatchMethodMethodConfig.
`minResourceCount`	`string (int64 format)` The minimum number of resources to be created for the overall request to be considered successful.
`errorRules`	`map (key: string, value: integer)` Canonical resource name to error status code mapping, implying the error rules to be returned by the apply CLH through the sidechannel.
`requestId`	`string` 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. 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` ).