Method: billingAccounts.billingAccountLicenseConfigs.distributeLicenseConfig

Distributes a LicenseConfig from billing account level to project level.

HTTP request

POST https://discoveryengine.googleapis.com/v1alpha/{billingAccountLicenseConfig=billingAccounts/*/billingAccountLicenseConfigs/*}:distributeLicenseConfig

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
billingAccountLicenseConfig

string

Required. Full resource name of BillingAccountLicenseConfig.

Format: billingAccounts/{billingAccount}/billingAccountLicenseConfigs/{billingAccountLicenseConfigId}.

Request body

The request body contains data with the following structure:

JSON representation 
{
  "projectNumber": string,
  "location": string,
  "licenseCount": string,
  "licenseConfigId": string
}
Fields
projectNumber

string (int64 format)

Required. The target GCP project number to distribute the license config to.
location

string

Required. The target GCP project region to distribute the license config to.
licenseCount

string (int64 format)

Required. The number of licenses to distribute.
licenseConfigId

string

Optional. Distribute seats to this license config instead of creating a new one. If not specified, a new license config will be created from the billing account license config.

Response body

Response message for LicenseConfigService.DistributeLicenseConfig method.

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

JSON representation 
{
  "licenseConfig": {
    object (LicenseConfig)
  }
}
Fields
licenseConfig

object (LicenseConfig)

The updated or created LicenseConfig.

Authorization scopes

Requires one of the following OAuth scopes:

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

For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the billingAccountLicenseConfig resource:

  • discoveryengine.billingAccountLicenseConfigs.distribute

For more information, see the IAM documentation.