mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Jun 29 09:00:05 UTC 2022
This commit is contained in:
parent
8b80260bd9
commit
cf5ab60e4a
195 changed files with 4700 additions and 413 deletions
|
|
@ -3,7 +3,7 @@ NAME
|
|||
using Google Cloud VMware Engine
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha vmware network-peerings COMMAND [GCLOUD_WIDE_FLAG ...]
|
||||
gcloud alpha vmware network-peerings GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Manage VMware Engine VPC peering using Google Cloud VMware Engine.
|
||||
|
|
@ -13,6 +13,13 @@ GCLOUD WIDE FLAGS
|
|||
|
||||
Run $ gcloud help for details.
|
||||
|
||||
GROUPS
|
||||
GROUP is one of the following:
|
||||
|
||||
routes
|
||||
(ALPHA) Manage VMware Engine VPC peering routes using Google Cloud
|
||||
VMware Engine.
|
||||
|
||||
COMMANDS
|
||||
COMMAND is one of the following:
|
||||
|
||||
|
|
|
|||
28
gcloud/alpha/vmware/network-peerings/routes/help
Normal file
28
gcloud/alpha/vmware/network-peerings/routes/help
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
NAME
|
||||
gcloud alpha vmware network-peerings routes - manage VMware Engine VPC
|
||||
peering routes using Google Cloud VMware Engine
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha vmware network-peerings routes COMMAND [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Manage VMware Engine VPC peering routes using Google Cloud VMware
|
||||
Engine.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --help.
|
||||
|
||||
Run $ gcloud help for details.
|
||||
|
||||
COMMANDS
|
||||
COMMAND is one of the following:
|
||||
|
||||
list
|
||||
(ALPHA) List Google Cloud VMware Engine VPC network peering routes.
|
||||
|
||||
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.
|
||||
|
||||
91
gcloud/alpha/vmware/network-peerings/routes/list
Normal file
91
gcloud/alpha/vmware/network-peerings/routes/list
Normal file
|
|
@ -0,0 +1,91 @@
|
|||
NAME
|
||||
gcloud alpha vmware network-peerings routes list - list Google Cloud VMware
|
||||
Engine VPC network peering routes
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha vmware network-peerings routes list
|
||||
--network-peering=NETWORK_PEERING [--filter=EXPRESSION] [--limit=LIMIT]
|
||||
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) List VPC network peering routes across all locations in your
|
||||
project.
|
||||
|
||||
EXAMPLES
|
||||
To list peering routes imported from peer network via my-peering:
|
||||
|
||||
$ gcloud alpha vmware network-peerings routes list \
|
||||
--network-peering=my-peering --filter="direction=INCOMING"
|
||||
|
||||
To list peering routes exported to peer network via my-peering:
|
||||
|
||||
$ gcloud alpha vmware network-peerings routes list \
|
||||
--network-peering=my-peering --filter="direction=OUTGOING"
|
||||
|
||||
In above examples, the location is taken as global.
|
||||
|
||||
REQUIRED FLAGS
|
||||
VMware Engine VPC network peering resource - network_peering. This
|
||||
represents a Cloud 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 --network-peering on the command line with a
|
||||
fully specified name;
|
||||
◆ set the property core/project;
|
||||
◆ provide the argument --project on the command line.
|
||||
|
||||
This must be specified.
|
||||
|
||||
--network-peering=NETWORK_PEERING
|
||||
ID of the VMware Engine VPC network peering or fully qualified
|
||||
identifier for the VMware Engine VPC network peering. To set the
|
||||
network-peering attribute:
|
||||
▸ provide the argument --network-peering on the command line.
|
||||
|
||||
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