Method: services.consumerQuotaMetrics.importConsumerOverrides

Creates or updates multiple consumer overrides atomically, all on the same consumer, but on many different metrics or limits. The name field in the quota override message should not be set.

HTTP request

POST https://serviceusage.googleapis.com/v1beta1/{parent=*/*/services/*}/consumerQuotaMetrics:importConsumerOverrides

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
parent

string

The resource name of the consumer.

An example name would be: projects/123/services/compute.googleapis.com

Authorization requires the following IAM permission on the specified resource parent:

  • serviceusage.quotas.update

Request body

The request body contains data with the following structure:

JSON representation
{
  "force": boolean,
  "forceOnly": [
    enum (QuotaSafetyCheck)
  ],

  // Union field source can be only one of the following:
  "inlineSource": {
    object (OverrideInlineSource)
  }
  // End of list of possible types for union field source.
}
Fields
force

boolean

Whether to force the creation of the quota overrides. Setting the force parameter to 'true' ignores all quota safety checks that would fail the request. QuotaSafetyCheck lists all such validations.

forceOnly[]

enum (QuotaSafetyCheck)

The list of quota safety checks to ignore before the override mutation. Unlike 'force' field that ignores all the quota safety checks, the 'forceOnly' field ignores only the specified checks; other checks are still enforced. The 'force' and 'forceOnly' fields cannot both be set.

Union field source. Source of import data source can be only one of the following:
inlineSource

object (OverrideInlineSource)

The import data is specified in the request message itself

Response body

If successful, the response body contains an instance of Operation.

Authorization scopes

Requires one of the following OAuth scopes:

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

For more information, see the Authentication Overview.