mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-16 12:22:03 +00:00
gcloud: Wed Dec 10 10:54:29 UTC 2025
This commit is contained in:
parent
7b14250313
commit
6d07e70b12
313 changed files with 11521 additions and 1088 deletions
|
|
@ -118,8 +118,11 @@ OPTIONAL FLAGS
|
|||
general-purpose-n4d, general-purpose-t2d, graphics-optimized,
|
||||
graphics-optimized-g4, memory-optimized, 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.
|
||||
memory-optimized-x4-1440-24t, memory-optimized-x4-16tb,
|
||||
memory-optimized-x4-1920-32t, memory-optimized-x4-24tb,
|
||||
memory-optimized-x4-32tb, memory-optimized-x4-480-6t,
|
||||
memory-optimized-x4-480-8t, memory-optimized-x4-960-12t,
|
||||
memory-optimized-x4-960-16t, storage-optimized-z3.
|
||||
|
||||
Manage the reservations to be created with the commitment.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,6 +24,9 @@ GROUPS
|
|||
blocks
|
||||
(ALPHA) Manage Compute Engine reservation blocks.
|
||||
|
||||
slots
|
||||
(ALPHA) Manage Compute Engine reservation slots.
|
||||
|
||||
sub-blocks
|
||||
(ALPHA) Manage Compute Engine reservation sub blocks.
|
||||
|
||||
|
|
|
|||
70
gcloud/alpha/compute/reservations/slots/describe
Normal file
70
gcloud/alpha/compute/reservations/slots/describe
Normal file
|
|
@ -0,0 +1,70 @@
|
|||
NAME
|
||||
gcloud alpha compute reservations slots describe - describe a Compute
|
||||
Engine reservation slot
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha compute reservations slots describe RESERVATION
|
||||
--block-name=BLOCK_NAME --slot-name=SLOT_NAME
|
||||
--sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Describe a Compute Engine reservation slot.
|
||||
|
||||
EXAMPLES
|
||||
To describe a reservation slot in reservation exr1 in my-zone with block
|
||||
name my-block, sub-block name my-sub-block, and slot name my-slot, run:
|
||||
|
||||
$ gcloud alpha compute reservations slots describe exr1 \
|
||||
--zone=my-zone --block-name=my-block \
|
||||
--sub-block-name=my-sub-block --slot-name=my-slot
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
RESERVATION
|
||||
Name of the reservation to describe.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--block-name=BLOCK_NAME
|
||||
The name of the reservation block.
|
||||
|
||||
--slot-name=SLOT_NAME
|
||||
The name of the reservation slot.
|
||||
|
||||
--sub-block-name=SUB_BLOCK_NAME
|
||||
The name of the reservation sub block.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--zone=ZONE
|
||||
Zone of the reservation to describe. If not specified and the
|
||||
compute/zone property isn't set, you might be prompted to select a zone
|
||||
(interactive mode only).
|
||||
|
||||
To avoid prompting when this flag is omitted, you can set the
|
||||
compute/zone property:
|
||||
|
||||
$ gcloud config set compute/zone ZONE
|
||||
|
||||
A list of zones can be fetched by running:
|
||||
|
||||
$ gcloud compute zones list
|
||||
|
||||
To unset the property, run:
|
||||
|
||||
$ gcloud config unset compute/zone
|
||||
|
||||
Alternatively, the zone can be stored in the environment variable
|
||||
CLOUDSDK_COMPUTE_ZONE.
|
||||
|
||||
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.
|
||||
|
||||
30
gcloud/alpha/compute/reservations/slots/help
Normal file
30
gcloud/alpha/compute/reservations/slots/help
Normal file
|
|
@ -0,0 +1,30 @@
|
|||
NAME
|
||||
gcloud alpha compute reservations slots - manage Compute Engine reservation
|
||||
slots
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha compute reservations slots COMMAND [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Manage Compute Engine reservation slots.
|
||||
|
||||
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 a Compute Engine reservation slot.
|
||||
|
||||
list
|
||||
(ALPHA) List Compute Engine reservation slots.
|
||||
|
||||
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.
|
||||
|
||||
109
gcloud/alpha/compute/reservations/slots/list
Normal file
109
gcloud/alpha/compute/reservations/slots/list
Normal file
|
|
@ -0,0 +1,109 @@
|
|||
NAME
|
||||
gcloud alpha compute reservations slots list - list Compute Engine
|
||||
reservation slots
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha compute reservations slots list RESERVATION
|
||||
--block-name=BLOCK_NAME --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE]
|
||||
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
|
||||
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute reservations slots list displays all Compute
|
||||
Engine reservation slots in an extended reservation's sub-block.
|
||||
|
||||
EXAMPLES
|
||||
To list all reservation slots in an extended reservation's block my-block
|
||||
and sub-block my-sub-block in table form, run:
|
||||
|
||||
$ gcloud alpha compute reservations slots list \
|
||||
extended-reservation --block-name=my-block \
|
||||
--sub-block-name=my-sub-block --zone=us-central1-a \
|
||||
--project=my-project
|
||||
|
||||
To list the URIs of all reservation slots in an extended reservation, run:
|
||||
|
||||
$ gcloud alpha compute reservations slots list \
|
||||
extended-reservation --block-name=my-block \
|
||||
--sub-block-name=my-sub-block --zone=us-central1-a \
|
||||
--project=my-project --uri
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
RESERVATION
|
||||
Name of the reservation to list.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--block-name=BLOCK_NAME
|
||||
The name of the reservation block.
|
||||
|
||||
--sub-block-name=SUB_BLOCK_NAME
|
||||
The name of the reservation sub block.
|
||||
|
||||
FLAGS
|
||||
--zone=ZONE
|
||||
Zone of the reservation to list. If not specified and the compute/zone
|
||||
property isn't set, you might be prompted to select a zone (interactive
|
||||
mode only).
|
||||
|
||||
To avoid prompting when this flag is omitted, you can set the
|
||||
compute/zone property:
|
||||
|
||||
$ gcloud config set compute/zone ZONE
|
||||
|
||||
A list of zones can be fetched by running:
|
||||
|
||||
$ gcloud compute zones list
|
||||
|
||||
To unset the property, run:
|
||||
|
||||
$ gcloud config unset compute/zone
|
||||
|
||||
Alternatively, the zone can be stored in the environment variable
|
||||
CLOUDSDK_COMPUTE_ZONE.
|
||||
|
||||
LIST COMMAND FLAGS
|
||||
--filter=EXPRESSION
|
||||
Apply a Boolean filter EXPRESSION to each resource item to be listed.
|
||||
If the expression evaluates True, then that item is listed. For more
|
||||
details and examples of filter expressions, run $ gcloud topic filters.
|
||||
This flag interacts with other flags that are applied in this order:
|
||||
--flatten, --sort-by, --filter, --limit.
|
||||
|
||||
--limit=LIMIT
|
||||
Maximum number of resources to list. The default is unlimited. This
|
||||
flag interacts with other flags that are applied in this order:
|
||||
--flatten, --sort-by, --filter, --limit.
|
||||
|
||||
--page-size=PAGE_SIZE
|
||||
Some services group resource list output into pages. This flag
|
||||
specifies the maximum number of resources per page. The default is
|
||||
determined by the service if it supports paging, otherwise it is
|
||||
unlimited (no paging). Paging may be applied before or after --filter
|
||||
and --limit depending on the service.
|
||||
|
||||
--sort-by=[FIELD,...]
|
||||
Comma-separated list of resource field key names to sort by. The
|
||||
default order is ascending. Prefix a field with ``~'' for descending
|
||||
order on that field. This flag interacts with other flags that are
|
||||
applied in this order: --flatten, --sort-by, --filter, --limit.
|
||||
|
||||
--uri
|
||||
Print a list of resource URIs instead of the default output, and change
|
||||
the command output to a list of URIs. If this flag is used with
|
||||
--format, the formatting is applied on this URI list. To display URIs
|
||||
alongside other keys instead, use the uri() transform.
|
||||
|
||||
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.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue