gcloud alpha compute routers add-route-policy-term

NAME

gcloud alpha compute routers add-route-policy-term - adds a new term to an existing route policy of a Comute Engine router

SYNOPSIS

gcloud alpha compute routers add-route-policy-term NAME --actions=[ACTION;…] --match=MATCH --policy-name=POLICY_NAME --priority=PRIORITY [--region=REGION] [GCLOUD_WIDE_FLAG …]

DESCRIPTION

(ALPHA) gcloud alpha compute routers add-route-policy-term adds a term to a route policy.

POSITIONAL ARGUMENTS

NAME

Name of the router to update.

REQUIRED FLAGS

--actions=[ACTION;…]

Semicolon separated CEL expressions for the actions to take when the rule matches.

--match=MATCH

CEL expression for matching a route.

--policy-name=POLICY_NAME

Name of the route policy to which to add the term.

--priority=PRIORITY

Order of the term within the policy.

OPTIONAL FLAGS

--region=REGION

Region of the router to update. If not specified, you might be prompted to select a region (interactive mode only).

To avoid prompting when this flag is omitted, you can set the compute/region property:

gcloud config set compute/region REGION

A list of regions can be fetched by running:

gcloud compute regions list

To unset the property, run:

gcloud config unset compute/region

Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION.

GCLOUD WIDE FLAGS

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.

NOTES

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. This variant is also available:

gcloud beta compute routers add-route-policy-term