- gcloud alpha compute backend-services edit - modify backend services
gcloud alpha compute backend-services edit BACKEND_SERVICE_NAME [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
(ALPHA) gcloud alpha compute backend-services edit can be used to
Backends are named by their associated instances groups, and one of the --group or --instance-group flags is required to identify the backend that you are modifying. You cannot "change" the instance group associated with a backend, but you can accomplish something similar with backend-services remove-backend and backend-services add-backend.
The editor used to modify the resource is chosen by inspecting the EDITOR environment variable.
Name of the backend service to operate on.
At most one of these may be specified:
If set, the backend service is global.
Region of the backend service to operate on. Overrides the default
compute/region property value for this command invocation.
- At most one of these may be specified:
GCLOUD WIDE FLAGS
These flags are available to all commands: --account, --configuration, --flags-file, --flatten, --format, --help, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details.
This command is currently in ALPHA and may change without notice. If this command fails with API permission errors despite specifying the right project, you will have to apply for early access and have your projects registered on the API whitelist to use it. To do so, contact Support at cloud.google.com/support These variants are also available:
- $ gcloud compute backend-services edit $ gcloud beta compute backend-services edit