imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 20:36:39 +00:00
Code Activity

gcloud: Wed Sep 27 12:05:40 UTC 2023

Browse source
This commit is contained in:
Automated 2023-09-27 12:05:40 +00:00
parent 54eca12593
commit 6c60d7f07f
256 changed files with 8313 additions and 442 deletions
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/alpha/compute/help
View file

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

4
gcloud/alpha/compute/instance-groups/managed/create
View file

@ -150,9 +150,9 @@ OPTIONAL FLAGS
Defines behaviour of using instances from standby pool to resize MIG.
STANDBY_POLICY_MODE must be one of:
MANUAL
manual
MIG does not automatically stop/start or suspend/resume VMs.
SCALE_OUT_POOL
scale-out-pool
MIG automatically resumes and starts VMs when it scales out, and
replenishes the standby pool afterwards.

4
gcloud/alpha/compute/instance-groups/managed/update
View file

@ -140,9 +140,9 @@ FLAGS
Defines behaviour of using instances from standby pool to resize MIG.
STANDBY_POLICY_MODE must be one of:
MANUAL
manual
MIG does not automatically stop/start or suspend/resume VMs.
SCALE_OUT_POOL
scale-out-pool
MIG automatically resumes and starts VMs when it scales out, and
replenishes the standby pool afterwards.

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

@ -0,0 +1,53 @@
NAME
gcloud alpha compute project-zonal-metadata add - add or update project
zonal metadata
SYNOPSIS
gcloud alpha compute project-zonal-metadata add
--metadata=KEY=VALUE,[KEY=VALUE,...] --zone=ZONE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) gcloud alpha 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 alpha 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 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.

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

@ -0,0 +1,36 @@
NAME
gcloud alpha compute project-zonal-metadata describe - describe project
zonal metadata
SYNOPSIS
gcloud alpha compute project-zonal-metadata describe --zone=ZONE
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) 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 alpha 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 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.

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

@ -0,0 +1,33 @@
NAME
gcloud alpha compute project-zonal-metadata - describe and update project
zonal metadata
SYNOPSIS
gcloud alpha compute project-zonal-metadata COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) 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
(ALPHA) Add or update project zonal metadata.
describe
(ALPHA) Describe project zonal metadata.
remove
(ALPHA) Remove project zonal metadata.
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.

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

@ -0,0 +1,60 @@
NAME
gcloud alpha compute project-zonal-metadata remove - remove project zonal
metadata
SYNOPSIS
gcloud alpha compute project-zonal-metadata remove --zone=ZONE
[--all | --keys=KEY,[KEY,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) gcloud alpha 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 alpha 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 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.

2
gcloud/alpha/compute/security-policies/rules/create
View file

@ -71,7 +71,7 @@ REQUIRED FLAGS
response status code of 404.
deny-502
Denies the request from HTTP(S) Load Balancing, with an HTTP
response status code of 503.
response status code of 502.
fairshare
When traffic reaches the threshold limit, requests from the clients
matching this rule begin to be rate-limited using the Fair Share

2
gcloud/alpha/compute/security-policies/rules/update
View file

@ -70,7 +70,7 @@ FLAGS
response status code of 404.
deny-502
Denies the request from HTTP(S) Load Balancing, with an HTTP
response status code of 503.
response status code of 502.
fairshare
When traffic reaches the threshold limit, requests from the clients
matching this rule begin to be rate-limited using the Fair Share

8
gcloud/alpha/compute/start-iap-tunnel
View file

@ -6,7 +6,7 @@ SYNOPSIS
[--iap-tunnel-disable-connection-check]
[--local-host-port=LOCAL_HOST_PORT; default="localhost:0"]
[--zone=ZONE]
[--network=NETWORK --region=REGION : --dest-group=DEST_GROUP]
[--region=REGION : [--network=NETWORK : --dest-group=DEST_GROUP]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -85,13 +85,13 @@ FLAGS
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
--region=REGION
Configures the region to use when connecting via IP address or FQDN.
--network=NETWORK
Configures the VPC network to use when connecting via IP address or
FQDN.
--region=REGION
Configures the region to use when connecting via IP address or FQDN.
--dest-group=DEST_GROUP
Configures the destination group to use when connecting via IP address
or FQDN.