imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Wed Sep 13 10:32:10 UTC 2023

Browse source
This commit is contained in:
Automated 2023-09-13 10:32:10 +00:00
parent 6c8d2eb024
commit 39a8a4f491
111 changed files with 1798 additions and 302 deletions
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/alpha/compute/help
View file

@ -166,6 +166,9 @@ GROUPS
shared-vpc
(ALPHA) Configure shared VPC.
snapshot-settings
(ALPHA) Describe and update Compute Engine snapshot settings.
snapshots
(ALPHA) List, describe, and delete Compute Engine snapshots.

27
gcloud/alpha/compute/images/export
View file

@ -4,6 +4,7 @@ NAME
SYNOPSIS
gcloud alpha compute images export --destination-uri=DESTINATION_URI
(--image=IMAGE | --image-family=IMAGE_FAMILY) [--async]
[--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT]
[--compute-service-account=COMPUTE_SERVICE_ACCOUNT]
[--export-format=EXPORT_FORMAT] [--image-project=IMAGE_PROJECT]
[--log-location=LOG_LOCATION] [--network=NETWORK] [--subnet=SUBNET]
@ -51,6 +52,28 @@ OPTIONAL FLAGS
Return immediately, without waiting for the operation in progress to
complete.
--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT
Image import amd export tools use Cloud Build to import and export
images to and from your project. Cloud Build uses a specific service
account to execute builds on your behalf. The Cloud Build service
account generates access token for other service accounts and it is
also used for authentication when building the artifacts for the image
import tool.
Use this flag to to specify a custom Cloud Build service account for
image import and export. If you don't specify this flag, Cloud Build
runs using your project's default Cloud Build service account. To set
this option, specify the email address corresponding to the required
Cloud Build service account. Note: You must specify the --logs-location
flag when you set the custom Cloud Build service account.
At minimum, the specified Cloud Build service account needs to have the
following roles assigned:
◆ roles/compute.admin
◆ roles/iam.serviceAccountTokenCreator
◆ roles/iam.serviceAccountUser
--compute-service-account=COMPUTE_SERVICE_ACCOUNT
A temporary virtual machine instance is created in your project during
image export. Image export tooling on this temporary instance must be
@ -66,8 +89,8 @@ OPTIONAL FLAGS
export on the temporary instance uses the project's default Compute
Engine service account.
At minimum, the specified Compute Engine service account needs to have
the following roles assigned:
At a minimum, you need to grant the following roles to the specified
Cloud Build service account:
◆ roles/compute.storageAdmin
◆ roles/storage.objectAdmin

27
gcloud/alpha/compute/images/import
View file

@ -10,6 +10,7 @@ SYNOPSIS
(--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH
| --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION
--aws-ami-id=AWS_AMI_ID)) [--no-address] [--async]
[--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT]
[--compute-service-account=COMPUTE_SERVICE_ACCOUNT]
[--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment]
[--guest-os-features=[GUEST_OS_FEATURE,...]]
@ -145,6 +146,28 @@ OPTIONAL FLAGS
Return immediately, without waiting for the operation in progress to
complete.
--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT
Image import amd export tools use Cloud Build to import and export
images to and from your project. Cloud Build uses a specific service
account to execute builds on your behalf. The Cloud Build service
account generates access token for other service accounts and it is
also used for authentication when building the artifacts for the image
import tool.
Use this flag to to specify a custom Cloud Build service account for
image import and export. If you don't specify this flag, Cloud Build
runs using your project's default Cloud Build service account. To set
this option, specify the email address corresponding to the required
Cloud Build service account. Note: You must specify the --logs-location
flag when you set the custom Cloud Build service account.
At minimum, the specified Cloud Build service account needs to have the
following roles assigned:
◆ roles/compute.admin
◆ roles/iam.serviceAccountTokenCreator
◆ roles/iam.serviceAccountUser
--compute-service-account=COMPUTE_SERVICE_ACCOUNT
A temporary virtual machine instance is created in your project during
image import. Image import tooling on this temporary instance must be
@ -160,8 +183,8 @@ OPTIONAL FLAGS
import on the temporary instance uses the project's default Compute
Engine service account.
At minimum, the specified Compute Engine service account needs to have
the following roles assigned:
At a minimum, you need to grant the following roles to the specified
Cloud Build service account:
◆ roles/compute.storageAdmin
◆ roles/storage.objectViewer

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

@ -9,13 +9,14 @@ SYNOPSIS
[--description=DESCRIPTION] [--[no-]force-update-on-repair]
[--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE]
[--list-managed-instances-results=MODE]
[--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY]
[--standby-pool-mode=STANDBY_POOL_MODE]
[--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY]
[--standby-policy-mode=STANDBY_POLICY_MODE]
[--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]]
[--stateful-external-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stateful-internal-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE]
[--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]]
[--zones=ZONE,[ZONE,...]]
[--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK
@ -142,12 +143,12 @@ OPTIONAL FLAGS
Pagination is enabled for the group's listManagedInstances API
method. maxResults and pageToken query parameters are respected.
--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY
--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY
Specifies the initialization delay for stopping/suspending instances.
--standby-pool-mode=STANDBY_POOL_MODE
--standby-policy-mode=STANDBY_POLICY_MODE
Defines behaviour of using instances from standby pool to resize MIG.
STANDBY_POOL_MODE must be one of:
STANDBY_POLICY_MODE must be one of:
MANUAL
MIG does not automatically stop/start or suspend/resume VMs.
@ -245,6 +246,12 @@ OPTIONAL FLAGS
the instance is deleted manually or when the group size is
decreased.
--stopped-size=STOPPED_SIZE
Specifies the number of stopped instances.
--suspended-size=SUSPENDED_SIZE
Specifies the number of suspended instances.
--target-distribution-shape=SHAPE
Specifies how a regional managed instance group distributes its
instances across zones within the region. The default shape is even.

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

@ -11,13 +11,14 @@ SYNOPSIS
[--remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...]]
[--remove-stateful-external-ips=INTERFACE_NAME,[...]]
[--remove-stateful-internal-ips=INTERFACE_NAME,[...]]
[--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY]
[--standby-pool-mode=STANDBY_POOL_MODE]
[--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY]
[--standby-policy-mode=STANDBY_POLICY_MODE]
[--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]]
[--stateful-external-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stateful-internal-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE]
[--target-distribution-shape=SHAPE]
[--clear-autohealing
| --initial-delay=INITIAL_DELAY --health-check=HEALTH_CHECK
@ -132,12 +133,12 @@ FLAGS
Remove stateful configuration for the specified interfaces for internal
IPs.
--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY
--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY
Specifies the initialization delay for stopping/suspending instances.
--standby-pool-mode=STANDBY_POOL_MODE
--standby-policy-mode=STANDBY_POLICY_MODE
Defines behaviour of using instances from standby pool to resize MIG.
STANDBY_POOL_MODE must be one of:
STANDBY_POLICY_MODE must be one of:
MANUAL
MIG does not automatically stop/start or suspend/resume VMs.
@ -248,6 +249,12 @@ FLAGS
the instance is deleted manually or when the group size is
decreased.
--stopped-size=STOPPED_SIZE
Specifies the number of stopped instances.
--suspended-size=SUSPENDED_SIZE
Specifies the number of suspended instances.
--target-distribution-shape=SHAPE
Specifies how a regional managed instance group distributes its
instances across zones within the region. The default shape is even.

27
gcloud/alpha/compute/instances/import
View file

@ -5,6 +5,7 @@ NAME
SYNOPSIS
gcloud alpha compute instances import INSTANCE_NAME --source-uri=SOURCE_URI
[--no-address] [--async] [--byol] [--can-ip-forward]
[--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT]
[--compute-service-account=COMPUTE_SERVICE_ACCOUNT]
[--deletion-protection] [--description=DESCRIPTION]
[--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]]
@ -89,6 +90,28 @@ OPTIONAL FLAGS
If provided, allows the instances to send and receive packets with
non-matching destination or source IP addresses.
--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT
Image import amd export tools use Cloud Build to import and export
images to and from your project. Cloud Build uses a specific service
account to execute builds on your behalf. The Cloud Build service
account generates access token for other service accounts and it is
also used for authentication when building the artifacts for the image
import tool.
Use this flag to to specify a custom Cloud Build service account for
image import and export. If you don't specify this flag, Cloud Build
runs using your project's default Cloud Build service account. To set
this option, specify the email address corresponding to the required
Cloud Build service account. Note: You must specify the --logs-location
flag when you set the custom Cloud Build service account.
At minimum, the specified Cloud Build service account needs to have the
following roles assigned:
◆ roles/compute.admin
◆ roles/iam.serviceAccountTokenCreator
◆ roles/iam.serviceAccountUser
--compute-service-account=COMPUTE_SERVICE_ACCOUNT
A temporary virtual machine instance is created in your project during
instance import. Instance import tooling on this temporary instance
@ -104,8 +127,8 @@ OPTIONAL FLAGS
import on the temporary instance uses the project's default Compute
Engine service account.
At minimum, the specified Compute Engine service account needs to have
the following roles assigned:
At a minimum, you need to grant the following roles to the specified
Cloud Build service account:
◆ roles/compute.storageAdmin
◆ roles/storage.objectViewer

27
gcloud/alpha/compute/machine-images/import
View file

@ -5,6 +5,7 @@ NAME
SYNOPSIS
gcloud alpha compute machine-images import IMAGE --source-uri=SOURCE_URI
[--no-address] [--async] [--byol] [--can-ip-forward]
[--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT]
[--compute-service-account=COMPUTE_SERVICE_ACCOUNT]
[--description=DESCRIPTION] [--no-guest-environment] [--guest-flush]
[--guest-os-features=[GUEST_OS_FEATURE,...]] [--labels=[KEY=VALUE,...]]
@ -88,6 +89,28 @@ OPTIONAL FLAGS
send and receive packets with non-matching destination or source IP
addresses.
--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT
Image import amd export tools use Cloud Build to import and export
images to and from your project. Cloud Build uses a specific service
account to execute builds on your behalf. The Cloud Build service
account generates access token for other service accounts and it is
also used for authentication when building the artifacts for the image
import tool.
Use this flag to to specify a custom Cloud Build service account for
image import and export. If you don't specify this flag, Cloud Build
runs using your project's default Cloud Build service account. To set
this option, specify the email address corresponding to the required
Cloud Build service account. Note: You must specify the --logs-location
flag when you set the custom Cloud Build service account.
At minimum, the specified Cloud Build service account needs to have the
following roles assigned:
◆ roles/compute.admin
◆ roles/iam.serviceAccountTokenCreator
◆ roles/iam.serviceAccountUser
--compute-service-account=COMPUTE_SERVICE_ACCOUNT
A temporary virtual machine instance is created in your project during
machine image import. Machine image import tooling on this temporary
@ -103,8 +126,8 @@ OPTIONAL FLAGS
image import on the temporary instance uses the project's default
Compute Engine service account.
At minimum, the specified Compute Engine service account needs to have
the following roles assigned:
At a minimum, you need to grant the following roles to the specified
Cloud Build service account:
◆ roles/compute.storageAdmin
◆ roles/storage.objectViewer

36
gcloud/alpha/compute/snapshot-settings/describe Normal file
View file

@ -0,0 +1,36 @@
NAME
gcloud alpha compute snapshot-settings describe - describe snapshot
settings
SYNOPSIS
gcloud alpha compute snapshot-settings describe [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Describe the snapshot settings of a project.
EXAMPLES
To display the snapshot settings of a project called my-project, run:
$ gcloud alpha compute snapshot-settings describe \
--project=my-project
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 compute/alpha API. The full documentation for this
API can be found at: https://cloud.google.com/compute/
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. This variant is also available:
$ gcloud beta compute snapshot-settings describe

32
gcloud/alpha/compute/snapshot-settings/help Normal file
View file

@ -0,0 +1,32 @@
NAME
gcloud alpha compute snapshot-settings - describe and update Compute Engine
snapshot settings
SYNOPSIS
gcloud alpha compute snapshot-settings COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Describe and update Compute Engine snapshot settings.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
(ALPHA) Describe snapshot settings.
update
(ALPHA) Update snapshot settings.
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. This variant is also available:
$ gcloud beta compute snapshot-settings

71
gcloud/alpha/compute/snapshot-settings/update Normal file
View file

@ -0,0 +1,71 @@
NAME
gcloud alpha compute snapshot-settings update - update snapshot settings
SYNOPSIS
gcloud alpha compute snapshot-settings update [--async]
[--storage-location-names=[STORAGE_LOCATION_NAMES,...]]
[--storage-location-policy=STORAGE_LOCATION_POLICY]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Update the snapshot settings of a project.
EXAMPLES
To update the snapshot settings and set the storage location policy to the
nearest multi-region as the source disk, run:
$ gcloud alpha compute snapshot-settings update \
--storage-location-policy=nearest-multi-region
To update the snapshot settings and set the storage location policy to the
same region as the source disk, run:
$ gcloud alpha compute snapshot-settings update \
--storage-location-policy=local-region
To update the snapshot settings and set the storage location policy to
store snapshots in a specific location like us-west1, run:
$ gcloud alpha compute snapshot-settings update \
--storage-location-policy=specific-locations \
--storage-location-names=us-west1
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--storage-location-names=[STORAGE_LOCATION_NAMES,...]
The custom storage locations that you specify for the project's
snapshots. Use this flag only when you use the SPECIFIC_LOCATIONS value
for the --storage-location-policy flag. For more information, refer to
the snapshot settings documentation at
https://cloud.google.com/compute/docs/disks/snapshot-settings.
--storage-location-policy=STORAGE_LOCATION_POLICY
The storage location policy. For more information, refer to the
snapshot settings documentation at
https://cloud.google.com/compute/docs/disks/snapshot-settings.
STORAGE_LOCATION_POLICY must be one of: local-region,
nearest-multi-region, specific-locations.
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 compute/alpha API. The full documentation for this
API can be found at: https://cloud.google.com/compute/
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. This variant is also available:
$ gcloud beta compute snapshot-settings update