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

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

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/beta/compute/help
View file

@ -132,6 +132,9 @@ GROUPS
project-info
(BETA) Read and manipulate project-level data like quotas and metadata.
project-zonal-metadata
(BETA) Describe and update project zonal metadata.
public-advertised-prefixes
(BETA) Manage public advertised prefix resources.

3
gcloud/beta/compute/network-attachments/help
View file

@ -28,6 +28,9 @@ COMMANDS
list
(BETA) List Google Compute Engine network attachments.
update
(BETA) Update a Google Compute Engine network attachment.
NOTES
This command is currently in beta and might change without notice. These
variants are also available:

92
gcloud/beta/compute/network-attachments/update Normal file
View file

@ -0,0 +1,92 @@
NAME
gcloud beta compute network-attachments update - update a Google Compute
Engine network attachment
SYNOPSIS
gcloud beta 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
(BETA) gcloud beta 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 beta 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 beta 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
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute network-attachments update
$ gcloud alpha compute network-attachments update

5
gcloud/beta/compute/networks/vpc-access/connectors/update
View file

@ -91,5 +91,8 @@ API REFERENCE
https://cloud.google.com/vpc/docs/configure-serverless-vpc-access
NOTES
This command is currently in beta and might change without notice.
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud compute networks vpc-access connectors update

53
gcloud/beta/compute/project-zonal-metadata/add Normal file
View file

@ -0,0 +1,53 @@
NAME
gcloud beta compute project-zonal-metadata add - add or update project
zonal metadata
SYNOPSIS
gcloud beta compute project-zonal-metadata add
--metadata=KEY=VALUE,[KEY=VALUE,...] --zone=ZONE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute project-zonal-metadata add is used to add or
update project zonal metadata for your VM instances. Project zonal metadata
values propagate to all VMs within the specified zone. Every VM has access
to a metadata server that you can use to query the configured project zonal
metadata values. To set metadata for individual instances, use gcloud
compute instances add-metadata. For information about metadata, see
https://cloud.google.com/compute/docs/metadata.
Only the metadata keys that you provide in the command get mutated. All
other existing metadata entries remain the same.
EXAMPLES
To set the project zonal metadata with key=value in the zone us-central1-a
for the project my-gcp-project, run:
$ gcloud beta compute project-zonal-metadata add \
--metadata=key=value --zone=us-central1-a \
--project=my-gcp-project
For more information and examples for setting project zonal metadata, see
https://cloud.google.com/compute/docs/metadata/setting-custom-metadata#set-custom-project-zonal-metadata
REQUIRED FLAGS
--metadata=KEY=VALUE,[KEY=VALUE,...]
The project zonal metadata key-value pairs that you want to add or
update
--zone=ZONE
The zone in which you want to add or update project zonal metadata
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha compute project-zonal-metadata add

36
gcloud/beta/compute/project-zonal-metadata/describe Normal file
View file

@ -0,0 +1,36 @@
NAME
gcloud beta compute project-zonal-metadata describe - describe project
zonal metadata
SYNOPSIS
gcloud beta compute project-zonal-metadata describe --zone=ZONE
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe project zonal metadata.
EXAMPLES
To describe the project zonal metadata in the zone us-central1-a for the
project my-gcp-project, run:
$ gcloud beta compute project-zonal-metadata describe \
--zone=us-central1-a --project=my-gcp-project
REQUIRED FLAGS
--zone=ZONE
Zone for project zonal metadata
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha compute project-zonal-metadata describe

33
gcloud/beta/compute/project-zonal-metadata/help Normal file
View file

@ -0,0 +1,33 @@
NAME
gcloud beta compute project-zonal-metadata - describe and update project
zonal metadata
SYNOPSIS
gcloud beta compute project-zonal-metadata COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe and update Compute Engine project zonal metadata.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
add
(BETA) Add or update project zonal metadata.
describe
(BETA) Describe project zonal metadata.
remove
(BETA) Remove project zonal metadata.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute project-zonal-metadata

60
gcloud/beta/compute/project-zonal-metadata/remove Normal file
View file

@ -0,0 +1,60 @@
NAME
gcloud beta compute project-zonal-metadata remove - remove project zonal
metadata
SYNOPSIS
gcloud beta compute project-zonal-metadata remove --zone=ZONE
[--all | --keys=KEY,[KEY,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute project-zonal-metadata remove is used to remove
project zonal metadata from all VMs within the specified zone. For
information about metadata, see
https://cloud.google.com/compute/docs/metadata.
Only the metadata keys that you provide in the command get removed. All
other existing metadata entries remain the same.
After you remove a specific project zonal metadata entry, if that metadata
key has any project-wide value configured, then the VMs in the zone
automatically inherit that project-wide value.
EXAMPLES
To remove the project zonal metadata with key=value in the zone
us-central1-a for the project my-gcp-project, run:
$ gcloud beta compute project-zonal-metadata remove --keys=key \
--zone=us-central1-a --project=my-gcp-project
For more information and examples about how to remove project zonal
metadata, see
https://cloud.google.com/compute/docs/metadata/setting-custom-metadata#remove-custom-project-zonal-metadata
REQUIRED FLAGS
--zone=ZONE
The zone in which you want to remove project zonal metadata
OPTIONAL FLAGS
At most one of these can be specified:
--all
If provided, all project zonal metadata entries are removed from VM
instances in the zone.
--keys=KEY,[KEY,...]
The keys for which you want to remove project zonal metadata
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha compute project-zonal-metadata remove