gcloud alpha services vpc-peerings update - update a private service connection to a service for a project network
gcloud alpha services vpc-peerings update --network=NETWORK [--async] [--force] [--ranges=RANGES] [--service=SERVICE; default="servicenetworking.googleapis.com"] [GCLOUD_WIDE_FLAG ...]
(ALPHA) This command updates a private service connection to a service via a VPC network.
To update connection for a network called my-network on the current project to a service called your-service with IP CIDR ranges google-range-1,google-range-2 for the service to use, run:
$ gcloud alpha services vpc-peerings update --network=my-network \ --service=your-service --ranges=google-range-1,google-range-2
To run the same command asynchronously (non-blocking), run:
$ gcloud alpha services vpc-peerings update --network=my-network \ --service=your-service --ranges=google-range-1,google-range-2 \ --async
- --network=NETWORK
The network in the current project to be peered with the service
- --async
Return immediately, without waiting for the operation in progress to complete.
- --force
If specified, the update call will proceed even if the update can be destructive.
- --ranges=RANGES
The names of IP CIDR ranges for service to use.
- --service=SERVICE; default="servicenetworking.googleapis.com"
The service to connect to
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 help for details.
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:
$ gcloud services vpc-peerings update
$ gcloud beta services vpc-peerings update