gcloud alpha compute url-maps validate - validate a URL map
gcloud alpha compute url-maps validate [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--source=SOURCE] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Runs static validation for the UrlMap. In particular, the tests of the provided UrlMap will be run. Calling this method does NOT create or update the UrlMap.
A URL map can be validated by running:
$ gcloud alpha compute url-maps validate --source=<path-to-file>
- --load-balancing-scheme=LOAD_BALANCING_SCHEME
Specifies the load balancer type(s) this validation request is for. Use EXTERNAL_MANAGED for HTTP/HTTPS External Global Load Balancer with Advanced Traffic Management. Use EXTERNAL for Classic HTTP/HTTPS External Global Load Balancer.
Other load balancer types are not supported. For more information, refer to Choosing a load balancer https://cloud.google.com/load-balancing/docs/choosing-load-balancer/.
If unspecified, the load balancing scheme will be inferred from the backend service resources this URL map references. If that can not be inferred (for example, this URL map only references backend buckets, or this URL map is for rewrites and redirects only and doesn't reference any backends), EXTERNAL will be used as the default type.
If specified, the scheme must not conflict with the load balancing scheme of the backend service resources this URL map references.
LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED.
- --source=SOURCE
Path to a YAML file containing configuration export data. The YAML file must not contain any output-only fields. Alternatively, you may omit this flag to read from standard input. For a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/UrlMap.yaml.
- At most one of these can be specified:
- --global
If set, the URL map is global.
- --region=REGION
Region of the URL map to validate.
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 compute url-maps validate
$ gcloud beta compute url-maps validate