1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 06:47:12 +00:00

gcloud: Wed Oct 25 11:42:23 UTC 2023

This commit is contained in:
Automated 2023-10-25 11:42:23 +00:00
parent a15665661a
commit d34c41a2ce
305 changed files with 5549 additions and 699 deletions

View file

@ -28,6 +28,9 @@ COMMANDS
list
List Google Compute Engine network attachments.
update
Update a Google Compute Engine network attachment.
NOTES
These variants are also available:

View file

@ -0,0 +1,91 @@
NAME
gcloud compute network-attachments update - update a Google Compute Engine
network attachment
SYNOPSIS
gcloud compute network-attachments update NAME [--description=DESCRIPTION]
[--producer-accept-list=[ACCEPT_LIST,...]]
[--producer-reject-list=[REJECT_LIST,...]] [--region=REGION]
[--subnets=SUBNETS,[SUBNETS,...]] [--subnets-region=SUBNETS_REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute network-attachments update is used to update network
attachments. You can update the following fields: description, subnets,
producer-accept-list and producer-reject-list. If you update the
producer-accept-list or producer-reject-list, the full new list should be
specified.
EXAMPLES
To update all the parameters with the new list, run:
$ gcloud compute network-attachments update \
NETWORK_ATTACHMENT_NAME --region=us-central1 \
--subnets=MY_SUBNET2 \
--description='default network attachment' \
--producer-accept-list=PROJECT5,PROJECT6 \
--producer-reject-list=PROJECT7,PROJECT8
To update a network attachment to change only the subnet to MY_SUBNET3,
run:
$ gcloud compute network-attachments update \
NETWORK_ATTACHMENT_NAME --region=us-central1 \
--subnets=MY_SUBNET3
POSITIONAL ARGUMENTS
NAME
Name of the network attachment to update.
FLAGS
--description=DESCRIPTION
An optional, textual description for the network attachment.
--producer-accept-list=[ACCEPT_LIST,...]
Projects that are allowed to connect to this network attachment.
--producer-reject-list=[REJECT_LIST,...]
Projects that are not allowed to connect to this network attachment.
--region=REGION
Region of the network attachment 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.
--subnets=SUBNETS,[SUBNETS,...]
The subnetworks provided by the consumer for the producers
--subnets-region=SUBNETS_REGION
Region of the subnetworks to operate on. Overrides the default
compute/region property value for this command invocation.
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
These variants are also available:
$ gcloud alpha compute network-attachments update
$ gcloud beta compute network-attachments update

View file

@ -52,7 +52,8 @@ FLAGS
network is used if unspecified.
This is only supported for NEGs with endpoint type gce-vm-ip-port,
non-gcp-private-ip-port, gce-vm-ip, or private-service-connect.
non-gcp-private-ip-port, gce-vm-ip, private-service-connect,
internet-ip-port, or internet-fqdn-port.
For Private Service Connect NEGs, you can optionally specify --network
and --subnet if --psc-target-service points to a published service. If

View file

@ -4,8 +4,9 @@ NAME
SYNOPSIS
gcloud compute network-endpoint-groups list-network-endpoints NAME
[--global | --zone=ZONE] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
[--global | --region=REGION | --zone=ZONE] [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List network endpoints in a network endpoint group.
@ -27,6 +28,26 @@ FLAGS
--global
If set, the network endpoint group is global.
--region=REGION
Region of the network endpoint group 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.
--zone=ZONE
Zone of the network endpoint group to operate on. If not specified
and the compute/zone property isn't set, you might be prompted to

View file

@ -6,8 +6,8 @@ SYNOPSIS
gcloud compute network-endpoint-groups update NAME
(--add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT]
| --remove-endpoint=[fqdn=FQDN],
[instance=INSTANCE],[ip=IP],[port=PORT]) [--global | --zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
[instance=INSTANCE],[ip=IP],[port=PORT])
[--global | --region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Update a Compute Engine network endpoint group.
@ -160,6 +160,26 @@ OPTIONAL FLAGS
--global
If set, the network endpoint group is global.
--region=REGION
Region of the network endpoint group 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.
--zone=ZONE
Zone of the network endpoint group to operate on. If not specified
and the compute/zone property isn't set, you might be prompted to

View file

@ -29,6 +29,9 @@ COMMANDS
list
List VPC Access connectors.
update
Update a VPC Access connector.
NOTES
This variant is also available:

View file

@ -0,0 +1,97 @@
NAME
gcloud compute networks vpc-access connectors update - update a VPC Access
connector
SYNOPSIS
gcloud compute networks vpc-access connectors update
(CONNECTOR : --region=REGION) [--async] [--machine-type=MACHINE_TYPE]
[--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Update an existing VPC Access connector with the given name.
This command can fail for the following reasons:
▪ Invalid parameters are passed to this command.
▪ The active account does not have permission to update instances.
EXAMPLES
The following command updates a VPC Access connector with name
my-vpc-connector in region us-central1:
$ gcloud compute networks vpc-access connectors update \
my-vpc-connector --region=us-central1 --min-instances=3 \
--max-instances=5
POSITIONAL ARGUMENTS
Connector resource - Arguments and flags that specify the VPC Access
connector you want to update. The arguments in this group can be used to
specify the attributes of this resource. (NOTE) Some attributes are not
given arguments in this group but can be set in other ways.
To set the project attribute:
◆ provide the argument connector on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
CONNECTOR
ID of the connector or fully qualified identifier for the connector.
To set the connector attribute:
▸ provide the argument connector on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--region=REGION
Compute region (e.g. us-central1) for the connector.
To set the region attribute:
▸ provide the argument connector on the command line with a fully
specified name;
▸ provide the argument --region on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--machine-type=MACHINE_TYPE
If set, updates the machine type of VMs underlying the connector.
Accepted values are "e2-micro", "f1-micro", and "e2-standard-4".
--max-instances=MAX_INSTANCES
If set, updates the maximum number of instances within an autoscaling
group underlying the connector. Value must be between 3 and 10,
inclusive, greater than or equal to the currently set maximum number of
instances, and greater than the value specified by --min-instances.
--min-instances must be provided.
--min-instances=MIN_INSTANCES
If set, updates the minimum number of instances within an autoscaling
group underlying the connector. Value must be between 2 and 9,
inclusive, greater than or equal to the currently set minimum number of
instances, and less than the value specified by --max-instances.
--max-instances must be provided
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.
API REFERENCE
This command uses the vpcaccess/v1 API. The full documentation for this API
can be found at:
https://cloud.google.com/vpc/docs/configure-serverless-vpc-access
NOTES
This variant is also available:
$ gcloud beta compute networks vpc-access connectors update

View file

@ -132,10 +132,13 @@ OPTIONAL FLAGS
For VM Endpoints
ENDPOINT_TYPE_SWG
For Secure Web Gateway Endpoints
ENDPOINT_TYPE_MANAGED_PROXY_LB
For regional Application Load Balancers (internal and external) and regional proxy Network Load Balancers (internal and external) endpoints
The default is ENDPOINT_TYPE_VM.
ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG.
ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG,
ENDPOINT_TYPE_MANAGED_PROXY_LB.
--icmp-idle-timeout=ICMP_IDLE_TIMEOUT
Timeout for ICMP connections. See

View file

@ -2,8 +2,10 @@ NAME
gcloud compute tpus tpu-vm update - update a Cloud TPU VM node
SYNOPSIS
gcloud compute tpus tpu-vm update (TPU : --zone=ZONE) [--async]
[--description=DESCRIPTION] [--internal-ips] [GCLOUD_WIDE_FLAG ...]
gcloud compute tpus tpu-vm update (TPU : --zone=ZONE)
[--add-tags=[TAGS,...]] [--async] [--description=DESCRIPTION]
[--internal-ips] [--clear-tags | --remove-tags=[TAG,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Update a Cloud TPU VM node.
@ -50,6 +52,12 @@ POSITIONAL ARGUMENTS
▸ set the property compute/zone.
FLAGS
--add-tags=[TAGS,...]
Tags to add to the TPU Node. Tags are used to identify valid sources or
targets for network firewalls. See
https://cloud.google.com/vpc/docs/add-remove-network-tags for more
details.
--async
Return immediately, without waiting for the operation in progress to
complete.
@ -62,6 +70,25 @@ FLAGS
default is that external IP addresses will be associated with the TPU
workers.
At most one of these can be specified:
--clear-tags
Remove all tags. If --add-tags is also specified then --clear-tags is
applied first.
For example, to remove all tags:
$ gcloud compute tpus tpu-vm update --clear-tags
To remove all existing tags and create two new tags, 'foo' and 'bar':
$ gcloud compute tpus tpu-vm update --clear-tags --add-tags foo,bar
--remove-tags=[TAG,...]
List of tags to remove. If a tag does not exist it is silently
ignored. If --add-tags is also specified then --add-tags is applied
first.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,