gcloud compute backend-services edit - modify a backend service
gcloud compute backend-services edit BACKEND_SERVICE_NAME [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
gcloud compute backend-services edit modifies a backend service of a Google Cloud load balancer or Traffic Director. The backend service resource is fetched from the server and presented in a text editor that displays the configurable fields.
The specific editor is defined by the EDITOR environment variable.
The name of each backend corresponds to the name of an instance group, zonal NEG, serverless NEG, or internet NEG.
To add, remove, or swap backends, use the gcloud compute backend-services remove-backend and gcloud compute backend-services add-backend commands.
- BACKEND_SERVICE_NAME
Name of the backend service to operate on.
- At most one of these can be specified:
- --global
If set, the backend service is global.
- --region=REGION
Region of the backend service to operate on. Overrides the default compute/region property value for this command invocation.
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.
These variants are also available:
$ gcloud alpha compute backend-services edit
$ gcloud beta compute backend-services edit