gcloud beta compute forwarding-rules update - update a Compute Engine forwarding rule

gcloud beta compute forwarding-rules updateNAME[--allow-global-access][--allow-psc-global-access][--external-managed-backend-bucket-migration-testing-percentage=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_TESTING_PERCENTAGE][--load-balancing-scheme=LOAD_BALANCING_SCHEME][--source-ip-ranges=SOURCE_IP_RANGE,[…]][--update-labels=[KEY=VALUE,…]][--clear-external-managed-backend-bucket-migration-state    |--external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE][--clear-labels    |--remove-labels=[KEY,…]][--global    |--region=REGION][GCLOUD_WIDE_FLAG …]

gcloudbetacomputeforwarding-rulesupdateexample-fr--allow-global-access--region=us-central1

To add/update labelsk0 andk1 and remove labels with keyk3, run:

gcloudbetacomputeforwarding-rulesupdateexample-fr--region=us-central1--update-labels=k0=value1,k1=value2--remove-labels=k3

Labels can be used to identify the forwarding rule and to filter them as in

gcloudbetacomputeforwarding-ruleslist--filter='labels.k1:value2'

To list existing labels, run:

gcloudbetacomputeforwarding-rulesdescribeexample-fr--format="default(labels)"

NAME

Name of the forwarding rule to operate on.

--allow-global-access

If True, then clients from all regions can access this internal forwarding rule.This can only be specified for forwarding rules with the LOAD_BALANCING_SCHEMEset to INTERNAL or INTERNAL_MANAGED. For forwarding rules of type INTERNAL, thetarget must be either a backend service or a target instance.

--allow-psc-global-access

If specified, clients from all regions can access this Private Service Connectforwarding rule. This can only be specified if the forwarding rule's target is aservice attachment (--target-service-attachment).

--external-managed-backend-bucket-migration-testing-percentage=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_TESTING_PERCENTAGE

Determines the fraction of requests that should be processed by the Globalexternal Application Load Balancer.

The value of this field must be in the range [0, 100].

--load-balancing-scheme=LOAD_BALANCING_SCHEME

Only for the Global external Application Load Balancer migration.

The value of this field must be EXTERNAL or EXTERNAL_MANAGED.

LOAD_BALANCING_SCHEME must be one of:EXTERNAL,EXTERNAL_MANAGED.

--source-ip-ranges=SOURCE_IP_RANGE,[…]

List of comma-separated IP addresses or IP ranges. If set, this forwarding ruleonly forwards traffic when the packet's source IP address matches one of the IPranges set here.

--update-labels=[KEY=VALUE,…]

List of label KEY=VALUE pairs to update. If a label exists, its value ismodified. Otherwise, a new label is created.

Keys must start with a lowercase character and contain only hyphens(-), underscores (_), lowercase characters, andnumbers. Values must contain only hyphens (-), underscores(_), lowercase characters, and numbers.

At most one of these can be specified:

--clear-external-managed-backend-bucket-migration-state

Clears current state of external managed migration.

--external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE

Specifies the migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE,and TEST_ALL_TRAFFIC.

To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must bechanged to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before theloadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, theTEST_BY_PERCENTAGE state can be used to migrate traffic to backend bucketsattached to this forwarding rule by percentage using the--external-managed-backend-bucket-migration-testing-percentage flag.

EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE must beone of:PREPARE,TEST_BY_PERCENTAGE,TEST_ALL_TRAFFIC.

At most one of these can be specified:

--clear-labels

Remove all labels. If--update-labels is also specified then--clear-labels is applied first.

For example, to remove all labels:

gcloudbetacomputeforwarding-rulesupdate--clear-labels

To remove all existing labels and create two new labels,foo andbaz:

gcloudbetacomputeforwarding-rulesupdate--clear-labels--update-labelsfoo=bar,baz=qux

--remove-labels=[KEY,…]

List of label keys to remove. If a label does not exist it is silently ignored.If--update-labels is also specified then--update-labels is applied first.

At most one of these can be specified:

--global

If set, the forwarding rule is global.

--region=REGION

Region of the forwarding rule to operate on. If not specified, you might beprompted to select a region (interactive mode only).

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

gcloudconfigsetcompute/regionREGION

A list of regions can be fetched by running:

gcloudcomputeregionslist

To unset the property, run:

gcloudconfigunsetcompute/region

Alternatively, the region can be stored in the environment variableCLOUDSDK_COMPUTE_REGION.

Run$gcloud help for details.