mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 23:08:48 +00:00
gcloud: Wed Apr 30 11:00:00 UTC 2025
This commit is contained in:
parent
4d8dd33b3e
commit
b03a332ad8
196 changed files with 7097 additions and 313 deletions
|
|
@ -108,14 +108,16 @@ OPTIONAL FLAGS
|
|||
for memory-optimized VMs. TYPE must be one of: accelerator-optimized,
|
||||
accelerator-optimized-a3, accelerator-optimized-a3-mega,
|
||||
accelerator-optimized-a3-ultra, accelerator-optimized-a4,
|
||||
compute-optimized, compute-optimized-c2d, compute-optimized-c3,
|
||||
compute-optimized-c3d, compute-optimized-h3, general-purpose,
|
||||
general-purpose-c4, general-purpose-c4a, general-purpose-e2,
|
||||
accelerator-optimized-a4x, compute-optimized, compute-optimized-c2d,
|
||||
compute-optimized-c3, compute-optimized-c3d, compute-optimized-h3,
|
||||
compute-optimized-h4d, general-purpose, general-purpose-c4,
|
||||
general-purpose-c4a, general-purpose-c4d, general-purpose-e2,
|
||||
general-purpose-n2, general-purpose-n2d, general-purpose-n4,
|
||||
general-purpose-t2d, graphics-optimized, memory-optimized,
|
||||
memory-optimized-m3, memory-optimized-m4, memory-optimized-x4,
|
||||
memory-optimized-x4-16tb, memory-optimized-x4-24tb,
|
||||
memory-optimized-x4-32tb, storage-optimized-z3.
|
||||
memory-optimized-m3, memory-optimized-m4, memory-optimized-m4-6tb,
|
||||
memory-optimized-x4, memory-optimized-x4-16tb,
|
||||
memory-optimized-x4-24tb, memory-optimized-x4-32tb,
|
||||
storage-optimized-z3.
|
||||
|
||||
Manage the reservations to be created with the commitment.
|
||||
|
||||
|
|
|
|||
|
|
@ -43,5 +43,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups add-members
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups add-members
|
||||
|
||||
|
|
|
|||
|
|
@ -64,5 +64,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups create
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups create
|
||||
|
||||
|
|
|
|||
|
|
@ -7,11 +7,19 @@ SYNOPSIS
|
|||
[NAME ...] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups delete
|
||||
deletes Compute Engine interconnect attachment groups. Interconnect
|
||||
attachment groups can be deleted even if they are referenced by
|
||||
interconnect attachments. Each interconnect attachment in the group will be
|
||||
updated to remove its reference to this group.
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups delete is
|
||||
used to delete interconnect attachment groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To delete an interconnect attachment group, run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups delete \
|
||||
example-attachment-group"
|
||||
|
||||
Although not shown in this example, you can delete multiple interconnect
|
||||
attachment groups in a single command.
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME [NAME ...]
|
||||
|
|
@ -29,5 +37,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups delete
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups delete
|
||||
|
||||
|
|
|
|||
|
|
@ -7,9 +7,16 @@ SYNOPSIS
|
|||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups describe
|
||||
displays all data associated with Compute Engine interconnect attachment
|
||||
group in a project.
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups describe is
|
||||
used to describe interconnect attachment groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To describe an interconnect attachment group, run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups describe \
|
||||
example-attachment-group
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
|
|
@ -27,5 +34,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups describe
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups describe
|
||||
|
||||
|
|
|
|||
|
|
@ -9,8 +9,17 @@ SYNOPSIS
|
|||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups
|
||||
get-operational-status gets the operational status of a Compute Engine
|
||||
interconnect attachment group in a project.
|
||||
get-operational-status is used to get the operational status of
|
||||
interconnect attachment groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To get the operational status of interconnect attachment group
|
||||
example-attachment-group, run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups \
|
||||
get-operational-status example-attachment-group
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
|
|
@ -28,5 +37,11 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups \
|
||||
get-operational-status
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups \
|
||||
get-operational-status
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ COMMANDS
|
|||
attachment group.
|
||||
|
||||
list
|
||||
(ALPHA) List Google Compute Engine interconnect attachment groups.
|
||||
(ALPHA) List interconnect attachment groups.
|
||||
|
||||
remove-members
|
||||
(ALPHA) Remove member interconnect attachments from a Compute Engine
|
||||
|
|
@ -48,5 +48,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
NAME
|
||||
gcloud alpha compute interconnects attachments groups list - list Google
|
||||
Compute Engine interconnect attachment groups
|
||||
gcloud alpha compute interconnects attachments groups list - list
|
||||
interconnect attachment groups
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha compute interconnects attachments groups list
|
||||
|
|
@ -8,18 +8,16 @@ SYNOPSIS
|
|||
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups list displays
|
||||
all Google Compute Engine interconnect attachment groups in a project.
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups list is used
|
||||
to list interconnect attachment groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To list all interconnect attachment groups in a project in table form, run:
|
||||
To list interconnect attachment groups, run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups list
|
||||
|
||||
To list the URIs of all interconnect attachment groups in a project, run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups list --uri
|
||||
|
||||
LIST COMMAND FLAGS
|
||||
--filter=EXPRESSION
|
||||
Apply a Boolean filter EXPRESSION to each resource item to be listed.
|
||||
|
|
@ -64,5 +62,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups list
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups list
|
||||
|
||||
|
|
|
|||
|
|
@ -43,5 +43,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups remove-members
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups remove-members
|
||||
|
||||
|
|
|
|||
|
|
@ -11,9 +11,35 @@ SYNOPSIS
|
|||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects attachments groups update is
|
||||
used to update interconnect attachment groups. An interconnect attachment
|
||||
group connects a set of redundant interconnect attachments between Google
|
||||
and the customer.
|
||||
used to update interconnect attachment groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To update an interconnect attachment group example-attachment-group's
|
||||
intended availability SLA to PRODUCTION_CRITICAL, run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups update \
|
||||
example-attachment-group \
|
||||
--intended-availability-sla=PRODUCTION_CRITICAL
|
||||
|
||||
To update an interconnect attachment group example-attachment-group's
|
||||
description to "example attachment group description", run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups update \
|
||||
example-attachment-group \
|
||||
--description="example attachment group description"
|
||||
|
||||
To update an interconnect attachment group example-attachment-group's
|
||||
member attachments to attachment-1 and attachment-2, run:
|
||||
|
||||
$ gcloud alpha compute interconnects attachments groups update \
|
||||
example-attachment-group \
|
||||
--attachments=region-1/attachment-1,region-2/attachment-2
|
||||
|
||||
Although you can add or remove member attachments using this command, it is
|
||||
recommended to add or remove member attachments using the add-members and
|
||||
remove-members commands.
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
|
|
@ -42,5 +68,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects attachments groups update
|
||||
|
||||
$ gcloud beta compute interconnects attachments groups update
|
||||
|
||||
|
|
|
|||
|
|
@ -40,5 +40,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups add-members
|
||||
|
||||
$ gcloud beta compute interconnects groups add-members
|
||||
|
||||
|
|
|
|||
|
|
@ -62,5 +62,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups create
|
||||
|
||||
$ gcloud beta compute interconnects groups create
|
||||
|
||||
|
|
|
|||
|
|
@ -24,10 +24,9 @@ EXAMPLES
|
|||
group example-interconnect-group, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups create-members \
|
||||
example-interconnect-group --interconnect-type DEDICATED \
|
||||
--link-speed LINK_TYPE_ETHERNET_10G_LR \
|
||||
--requested-link-count 1 --facility iad-1 \
|
||||
--interconnect="name=interconnect1" \
|
||||
example-interconnect-group --interconnect-type=DEDICATED \
|
||||
--link-type=LINK_TYPE_ETHERNET_10G_LR --requested-link-count=1 \
|
||||
--facility=iad-1 --interconnect="name=interconnect1" \
|
||||
--interconnect="name=interconnect2"
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
|
|
@ -133,5 +132,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups create-members
|
||||
|
||||
$ gcloud beta compute interconnects groups create-members
|
||||
|
||||
|
|
|
|||
|
|
@ -7,10 +7,19 @@ SYNOPSIS
|
|||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects groups delete deletes Compute
|
||||
Engine interconnect groups. Interconnect groups can be deleted even if they
|
||||
are referenced by interconnects. Each interconnect in the group will be
|
||||
updated to remove its reference to this group.
|
||||
(ALPHA) gcloud alpha compute interconnects groups delete is used to delete
|
||||
interconnect groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To delete an interconnect group, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups delete \
|
||||
example-interconnect-group"
|
||||
|
||||
Although not shown in this example, you can delete multiple interconnect
|
||||
groups in a single command.
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME [NAME ...]
|
||||
|
|
@ -28,5 +37,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups delete
|
||||
|
||||
$ gcloud beta compute interconnects groups delete
|
||||
|
||||
|
|
|
|||
|
|
@ -7,8 +7,16 @@ SYNOPSIS
|
|||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects groups describe displays all
|
||||
data associated with Compute Engine interconnect group in a project.
|
||||
(ALPHA) gcloud alpha compute interconnects groups describe is used to
|
||||
describe an interconnect group.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To describe interconnect group example-interconnect-group, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups describe \
|
||||
example-interconnect-group
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
|
|
@ -26,5 +34,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups describe
|
||||
|
||||
$ gcloud beta compute interconnects groups describe
|
||||
|
||||
|
|
|
|||
|
|
@ -7,9 +7,17 @@ SYNOPSIS
|
|||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects groups get-operational-status
|
||||
gets the operational status of a Compute Engine interconnect group in a
|
||||
project.
|
||||
(ALPHA) gcloud alpha compute interconnects groups get-operational-status is
|
||||
used to get the operational status of an interconnect group.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To get the operational status of interconnect group
|
||||
example-interconnect-group, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups get-operational-status \
|
||||
example-interconnect-group
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
|
|
@ -27,5 +35,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups get-operational-status
|
||||
|
||||
$ gcloud beta compute interconnects groups get-operational-status
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ COMMANDS
|
|||
group.
|
||||
|
||||
list
|
||||
(ALPHA) List Google Compute Engine interconnect groups.
|
||||
(ALPHA) List interconnect groups.
|
||||
|
||||
remove-members
|
||||
(ALPHA) Remove member interconnects from a Compute Engine interconnect
|
||||
|
|
@ -51,5 +51,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups
|
||||
|
||||
$ gcloud beta compute interconnects groups
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
NAME
|
||||
gcloud alpha compute interconnects groups list - list Google Compute Engine
|
||||
interconnect groups
|
||||
gcloud alpha compute interconnects groups list - list interconnect groups
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha compute interconnects groups list [--filter=EXPRESSION]
|
||||
|
|
@ -8,18 +7,16 @@ SYNOPSIS
|
|||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects groups list displays all Google
|
||||
Compute Engine interconnect groups in a project.
|
||||
(ALPHA) gcloud alpha compute interconnects groups list is used to list
|
||||
interconnect groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To list all interconnect groups in a project in table form, run:
|
||||
To list interconnect groups, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups list
|
||||
|
||||
To list the URIs of all interconnect groups in a project, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups list --uri
|
||||
|
||||
LIST COMMAND FLAGS
|
||||
--filter=EXPRESSION
|
||||
Apply a Boolean filter EXPRESSION to each resource item to be listed.
|
||||
|
|
@ -64,5 +61,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups list
|
||||
|
||||
$ gcloud beta compute interconnects groups list
|
||||
|
||||
|
|
|
|||
|
|
@ -40,5 +40,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups remove-members
|
||||
|
||||
$ gcloud beta compute interconnects groups remove-members
|
||||
|
||||
|
|
|
|||
|
|
@ -10,8 +10,35 @@ SYNOPSIS
|
|||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute interconnects groups update is used to update
|
||||
interconnect groups. An interconnect group represents a set of redundant
|
||||
interconnects between Google and the customer.
|
||||
interconnect groups.
|
||||
|
||||
For an example, refer to the EXAMPLES section below.
|
||||
|
||||
EXAMPLES
|
||||
To update an interconnect group example-interconnect-group's intended
|
||||
topology capability to PRODUCTION_CRITICAL, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups update \
|
||||
example-interconnect-group \
|
||||
--intended-topology-capability=PRODUCTION_CRITICAL
|
||||
|
||||
To update an interconnect group example-interconnect-group's description to
|
||||
"example interconnect group description", run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups update \
|
||||
example-interconnect-group \
|
||||
--description="example interconnect group description"
|
||||
|
||||
To update an interconnect group example-interconnect-group's member
|
||||
interconnects to interconnect-1 and interconnect-2, run:
|
||||
|
||||
$ gcloud alpha compute interconnects groups update \
|
||||
example-interconnect-group \
|
||||
--interconnects=interconnect-1,interconnect-2
|
||||
|
||||
Although you can add or remove member interconnects using this command, it
|
||||
is recommended to add or remove member interconnects using the add-members
|
||||
and remove-members commands.
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
NAME
|
||||
|
|
@ -40,5 +67,9 @@ 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.
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute interconnects groups update
|
||||
|
||||
$ gcloud beta compute interconnects groups update
|
||||
|
||||
|
|
|
|||
|
|
@ -48,6 +48,8 @@ REQUIRED FLAGS
|
|||
deny-502
|
||||
Denies the request from HTTP(S) Load Balancing, with an HTTP
|
||||
response status code of 502.
|
||||
goto-next
|
||||
Defers enforcement to the next policy in the hierarchy.
|
||||
redirect
|
||||
Redirects the request from HTTP(S) Load Balancing, based on
|
||||
redirect options.
|
||||
|
|
|
|||
|
|
@ -54,6 +54,8 @@ OPTIONAL FLAGS
|
|||
deny-502
|
||||
Denies the request from HTTP(S) Load Balancing, with an HTTP
|
||||
response status code of 502.
|
||||
goto-next
|
||||
Defers enforcement to the next policy in the hierarchy.
|
||||
redirect
|
||||
Redirects the request from HTTP(S) Load Balancing, based on
|
||||
redirect options.
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ DESCRIPTION
|
|||
|
||||
To remove the default service account from the project, issue the command:
|
||||
|
||||
$ gcloud compute project-info set-default-service-account \
|
||||
$ gcloud alpha compute project-info set-default-service-account \
|
||||
--no-service-account
|
||||
|
||||
The required permission to execute this command is
|
||||
|
|
|
|||
|
|
@ -13,9 +13,11 @@ SYNOPSIS
|
|||
[--consumer-reject-list=[REJECT_LIST,...]] [--description=DESCRIPTION]
|
||||
[--domain-names=[DOMAIN_NAMES,...]] [--enable-proxy-protocol]
|
||||
[--nat-subnets-region=NAT_SUBNETS_REGION]
|
||||
[--producer-forwarding-rule-region=PRODUCER_FORWARDING_RULE_REGION]
|
||||
[--propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT]
|
||||
[--reconcile-connections] [--region=REGION] [GCLOUD_WIDE_FLAG ...]
|
||||
[--reconcile-connections] [--region=REGION]
|
||||
[--global-producer-forwarding-rule
|
||||
| --producer-forwarding-rule-region=PRODUCER_FORWARDING_RULE_REGION]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute service-attachments create is used to create
|
||||
|
|
@ -114,26 +116,6 @@ OPTIONAL FLAGS
|
|||
set to the region of the service attachment. Overrides the default
|
||||
compute/region property value for this command invocation.
|
||||
|
||||
--producer-forwarding-rule-region=PRODUCER_FORWARDING_RULE_REGION
|
||||
Region of the forwarding rule to operate on. 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.
|
||||
|
||||
--propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT
|
||||
The number of consumer spokes that connected Private Service Connect
|
||||
endpoints can be propagated to through Network Connectivity Center.
|
||||
|
|
@ -183,6 +165,31 @@ OPTIONAL FLAGS
|
|||
Alternatively, the region can be stored in the environment variable
|
||||
CLOUDSDK_COMPUTE_REGION.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--global-producer-forwarding-rule
|
||||
If set, the forwarding rule is global.
|
||||
|
||||
--producer-forwarding-rule-region=PRODUCER_FORWARDING_RULE_REGION
|
||||
Region of the forwarding rule to operate on. 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,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue