ControlPlaneAccess is the request body and response body of organizations.updateControlPlaneAccess
. and the response body of organizations.getControlPlaneAccess
.
The input identities contains an array of service accounts to grant access to the respective control plane resource, with each service account specified using the following format: serviceAccount:
***service-account-name***.
The service-account-name is formatted like an email address. For example: my-control-plane-serviceAccount@my_project_id.iam.gserviceaccount.com
You might specify multiple service accounts, for example, if you have multiple environments and wish to assign a unique service account to each one.
JSON representation |
---|
{ "name": string, "synchronizerIdentities": [ string ], "analyticsPublisherIdentities": [ string ] } |
Fields | |
---|---|
name |
Identifier. The resource name of the ControlPlaneAccess. Format: "organizations/{org}/controlPlaneAccess" |
synchronizer |
Optional. Array of service accounts to grant access to control plane resources (for the Synchronizer component). The service accounts must have Apigee Synchronizer Manager role. See also Create service accounts. |
analytics |
Optional. Array of service accounts authorized to publish analytics data to the control plane (for the Message Processor component). |