- gcloud alpha compute target-ssl-proxies update - update a target SSL proxy
gcloud alpha compute target-ssl-proxies update NAME [--backend-service=BACKEND_SERVICE] [--proxy-header=PROXY_HEADER] [--ssl-certificates=SSL_CERTIFICATE,[...]] [--clear-ssl-policy | --ssl-policy=SSL_POLICY] [GCLOUD_WIDE_FLAG ...]
(ALPHA) gcloud alpha compute target-ssl-proxies update is used to
Name of the target SSL proxy to update.
A backend service that will be used for connections to the target SSL proxy.
The type of proxy protocol header to be sent to the backend. PROXY_HEADER
must be one of:
- No proxy header is added.
- Enables PROXY protocol (version 1) for passing client connection information.
References to at most 10 SSL certificate resources that are used for
server-side authentication. The first SSL certificate in this list is
considered the primary SSL certificate associated with the load balancer. The
SSL certificate must exist and cannot be deleted while referenced by a target
At most one of these may be specified:
Removes any attached SSL policy from the SSL proxy.
A reference to an SSL policy resource that defines the server-side support for
SSL features and affects the connections between clients and the SSL proxy load
balancer. The SSL policy must exist and cannot be deleted while referenced by a
target SSL proxy.
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 target-ssl-proxies update $ gcloud beta compute target-ssl-proxies update