ControlPlaneAccess
ControlPlaneAccess is the request body and response body oforganizations.updateControlPlaneAccess. and the response body oforganizations.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***.
Theservice-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" |
synchronizerIdentities[] |
Optional. Array of service accounts to grant access to control plane resources (for the Synchronizer component). The service accounts must haveApigee Synchronizer Manager role. See alsoCreate service accounts. |
analyticsPublisherIdentities[] |
Optional. Array of service accounts authorized to publish analytics data to the control plane (for the Message Processor component). |
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.