gcloud alpha compute service-attachments update Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud alpha compute service-attachments update - update a Google Compute Engine service attachment
- SYNOPSIS
gcloud alpha compute service-attachments updateNAME[--connection-preference=CONNECTION_PREFERENCE][--consumer-accept-list=[PROJECT_OR_NETWORK_OR_ENDPOINT=LIMIT,…]][--consumer-reject-list=[REJECT_LIST,…]][--description=DESCRIPTION][--[no-]enable-proxy-protocol][--nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,…]][--nat-subnets-region=NAT_SUBNETS_REGION][--propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT][--[no-]reconcile-connections][--region=REGION][--target-service=TARGET_SERVICE][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(ALPHA)gcloud alpha compute service-attachmentsupdateis used to update service attachments. A service producer createsservice attachments to make a service available to consumers. Service consumersuse Private Service Connect endpoints to privately forward traffic to theservice attachment.- EXAMPLES
- To update the connection policy of a service attachment to be ACCEPT_MANUAL,run:
gcloudalphacomputeservice-attachmentsupdateSERVICE_ATTACHMENT_NAME--region=us-central1--connection-preference=ACCEPT_MANUALTo update all supported fields of a service attachment, run:
gcloudalphacomputeservice-attachmentsupdateSERVICE_ATTACHMENT_NAME--region=us-central1--connection-preference=ACCEPT_AUTOMATIC--nat-subnets=MY_SUBNET1,MY_SUBNET2--enable-proxy-protocol--consumer-reject-list=PROJECT_ID1,PROJECT_ID2--consumer-accept-list=PROJECT_ID3=10,PROJECT_ID4=20 - POSITIONAL ARGUMENTS
NAME- Name of the service attachment to update.
- FLAGS
--connection-preference=CONNECTION_PREFERENCE- This defines the service attachment's connection preference.
CONNECTION_PREFERENCEmust be one of:ACCEPT_AUTOMATIC- Always accept connection requests from consumers automatically.
ACCEPT_MANUAL- Only accept connection requests from consumers with the approval of the serviceprovider.
--consumer-accept-list=[PROJECT_OR_NETWORK_OR_ENDPOINT=LIMIT,…]- Specifies which consumer projects/networks/endpoints are allowed to connect tothe service attachment. Each project or network has a connection limit. Forendpoints, the connection limit is optional. Both the accept and reject listsfor a given service attachment must contain either only one of projects,networks or endpoints.
For example,
--consumer-accept-list myProjectId1=20accepts aconsumer project myProjectId1 with connection limit 20;--consumer-accept-listprojects/myProjectId1/global/networks/myNet1=20accepts a consumernetwork myNet1 with connection limit 20--consumer-accept-listprojects/myProjectId1/regions/myRegion1/forwardingRules/8167352512alsoaccepts a consumer endpoint with ID 8167352512.PROJECT_OR_NETWORK_OR_ENDPOINT- Consumer project ID/number ornetwork URL orendpoint URL.CONNECTION_LIMIT- The maximum number of allowed connections.
--consumer-reject-list=[REJECT_LIST,…]- Specifies a comma separated list of projects or networks that are not allowed toconnect to this service attachment. The project can be specified using itsproject ID or project number and the network can be specified using its URL. Agiven service attachment can manage connections at either the project or networklevel. Therefore, both the reject and accept lists for a given serviceattachment must contain either only projects or only networks.
--description=DESCRIPTION- An optional, textual description for the service attachment.
--[no-]enable-proxy-protocol- If True, then enable the proxy protocol which is for supplying client TCP/IPaddress data in TCP connections that traverse proxies on their way todestination servers. Use
--enable-proxy-protocolto enable and--no-enable-proxy-protocolto disable. --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,…]- The subnetworks provided by service producer to use for NAT
--nat-subnets-region=NAT_SUBNETS_REGION- Region of the subnetworks to operate on. If not specified, it will be set to theregion of the service attachment. Overrides the default
compute/regionproperty value for this command invocation. --propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT- The number of consumer spokes that connected Private Service Connect endpointscan be propagated to through Network Connectivity Center. This limit lets theservice producer limit how many propagated Private Service Connect connectionscan be established to this service attachment from a single consumer.
If the connection preference of the service attachment is ACCEPT_MANUAL, thelimit applies to each project or network that is listed in the consumer acceptlist. If the connection preference of the service attachment isACCEPT_AUTOMATIC, the limit applies to each project that contains a connectedendpoint.
If unspecified, the default propagated connection limit is 250.
--[no-]reconcile-connections- Determines whether to apply changes to consumer accept or reject lists toexisting connections or only to new connections.
If false, existing endpoints with a connection status of ACCEPTED or REJECTEDare not updated.
If true, existing endpoints with a connection status of ACCEPTED or REJECTED areupdated based on the connection policy update. For example, if a project ornetwork is removed from the --consumer-accept-list and added to--consumer-reject-list, all the endpoints in that project or network with theACCEPTED state are set to REJECTED.
Use
--reconcile-connectionsto enable and--no-reconcile-connectionsto disable. --region=REGION- Region of the service attachment to update. If not specified, you might beprompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
property:compute/regiongcloudconfigsetcompute/regionREGIONA list of regions can be fetched by running:
gcloudcomputeregionslistTo unset the property, run:
gcloudconfigunsetcompute/regionAlternatively, the region can be stored in the environment variable
.CLOUDSDK_COMPUTE_REGION --target-service=TARGET_SERVICE- URL of the target service that receives forwarded traffic.
- GCLOUD WIDE FLAGS
- These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$gcloud helpfor details. - NOTES
- This command is currently in alpha and might change without notice. If thiscommand fails with API permission errors despite specifying the correct project,you might be trying to access an API with an invitation-only early accessallowlist. These variants are also available:
gcloudcomputeservice-attachmentsupdategcloudbetacomputeservice-attachmentsupdate
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-10-14 UTC.