1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-17 22:36:52 +00:00

gcloud: Wed Nov 15 11:42:54 UTC 2023

This commit is contained in:
Automated 2023-11-15 11:42:54 +00:00
parent 03f0979970
commit d3074f94bb
224 changed files with 6432 additions and 626 deletions

View file

@ -0,0 +1,101 @@
NAME
gcloud vmware private-clouds logging-servers create - create a Google Cloud
VMware Engine logging-server
SYNOPSIS
gcloud vmware private-clouds logging-servers create
(LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD)
--hostname=HOSTNAME --port=PORT --protocol=PROTOCOL
--source-type=SOURCE_TYPE [--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Create a logging-server in a VMware Engine private cloud to forward VCSA or
ESXI logs to it.
EXAMPLES
To create a logging-server called my-logging-server in private cloud
my-private-cloud, with source type ESXI, host name 192.168.0.30, protocol
UDP and port 514, run:
$ gcloud vmware private-clouds logging-servers create \
my-logging-server --location=us-west2-a --project=my-project \
--private-cloud=my-private-cloud --source-type=ESXI \
--hostname=192.168.0.30 --protocol=UDP --port=514
Or:
$ gcloud vmware private-clouds logging-servers create \
my-logging-server --private-cloud=my-private-cloud \
--source-type=ESXI --hostname=192.168.0.30 --protocol=UDP \
--port=514
In the second example, the project and location are taken from gcloud properties core/project and compute/zone.
POSITIONAL ARGUMENTS
Logging Server resource - logging_server. The arguments in this group can
be used to specify the attributes of this 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 logging_server 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.
LOGGING_SERVER
ID of the Logging Server or fully qualified identifier for the
Logging Server.
To set the logging-server attribute:
▸ provide the argument logging_server on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location of the private cloud or cluster.
To set the location attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --location on the command line;
▸ set the property compute/zone.
--private-cloud=PRIVATE_CLOUD
VMware Engine private cloud.
To set the private-cloud attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --private-cloud on the command line.
REQUIRED FLAGS
--hostname=HOSTNAME
Fully-qualified domain name (FQDN) or IP Address of the logging server.
--port=PORT
Port number at which the logging server receives logs.
--protocol=PROTOCOL
Defines possible protocols used to send logs to a logging server.
PROTOCOL must be one of: UDP, TCP.
--source-type=SOURCE_TYPE
The type of component that produces logs that will be forwarded to this
logging server. SOURCE_TYPE must be one of: VCSA, ESXI.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete. The default is True. Enabled by default, use --no-async to
disable.
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.

View file

@ -0,0 +1,81 @@
NAME
gcloud vmware private-clouds logging-servers delete - delete logging-server
from a VMware Engine private cloud
SYNOPSIS
gcloud vmware private-clouds logging-servers delete
(LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD)
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Delete logging-server from a VMware Engine private cloud.
EXAMPLES
To delete an logging-server called my-logging-server in private cloud
my-private-cloud and location us-east2-b, run:
$ gcloud vmware private-clouds logging-servers delete \
my-logging-server --private-cloud=my-private-cloud \
--location=us-east2-b --project=my-project
Or:
$ gcloud vmware private-clouds logging-servers delete \
my-logging-server --private-cloud=my-private-cloud
In the second example, the project and region are taken from gcloud
properties core/project and vmware/region.
POSITIONAL ARGUMENTS
Logging Server resource - logging_server. The arguments in this group can
be used to specify the attributes of this 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 logging_server 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.
LOGGING_SERVER
ID of the Logging Server or fully qualified identifier for the
Logging Server.
To set the logging-server attribute:
▸ provide the argument logging_server on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location of the private cloud or cluster.
To set the location attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --location on the command line;
▸ set the property compute/zone.
--private-cloud=PRIVATE_CLOUD
VMware Engine private cloud.
To set the private-cloud attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --private-cloud on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete. The default is True. Enabled by default, use --no-async to
disable.
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.

View file

@ -0,0 +1,75 @@
NAME
gcloud vmware private-clouds logging-servers describe - describe a Google
Cloud VMware Engine logging-server
SYNOPSIS
gcloud vmware private-clouds logging-servers describe
(LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD)
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Display data associated with a VMware Engine logging-server, such as its
host name, port, protocol, and source type.
EXAMPLES
To describe a logging-server called my-logging-server in private cloud
my-private-cloud and zone us-west2-a, run:
$ gcloud vmware private-clouds logging-servers describe \
my-logging-server --location=us-west2-a --project=my-project \
--private-cloud=my-private-cloud
Or:
$ gcloud vmware private-clouds logging-servers describe \
my-logging-server --private-cloud=my-private-cloud
In the second example, the project and location are taken from gcloud properties core/project and compute/zone.
POSITIONAL ARGUMENTS
Logging Server resource - logging_server. The arguments in this group can
be used to specify the attributes of this 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 logging_server 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.
LOGGING_SERVER
ID of the Logging Server or fully qualified identifier for the
Logging Server.
To set the logging-server attribute:
▸ provide the argument logging_server on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location of the private cloud or cluster.
To set the location attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --location on the command line;
▸ set the property compute/zone.
--private-cloud=PRIVATE_CLOUD
VMware Engine private cloud.
To set the private-cloud attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --private-cloud on the command line.
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.

View file

@ -0,0 +1,32 @@
NAME
gcloud vmware private-clouds logging-servers - manage logging-server in
Google Cloud VMware Engine
SYNOPSIS
gcloud vmware private-clouds logging-servers COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Manage logging-server in 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:
create
Create a Google Cloud VMware Engine logging-server.
delete
Delete logging-server from a VMware Engine private cloud.
describe
Describe a Google Cloud VMware Engine logging-server.
list
List logging-server in a Google Cloud VMware Engine private cloud.
update
Update a Google Cloud VMware Engine logging-server.

View file

@ -0,0 +1,99 @@
NAME
gcloud vmware private-clouds logging-servers list - list logging-server in
a Google Cloud VMware Engine private cloud
SYNOPSIS
gcloud vmware private-clouds logging-servers list
(--private-cloud=PRIVATE_CLOUD : --location=LOCATION)
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List logging-server in a VMware Engine private cloud.
EXAMPLES
To list logger-server in the my-private-cloud private cloud run:
$ gcloud vmware private-clouds logging-servers list \
--location=us-west2-a --project=my-project \
--private-cloud=my-private-cloud
Or:
$ gcloud vmware private-clouds logging-servers list \
--private-cloud=my-private-cloud
In the second example, the project and location are taken from gcloud
properties core/project and compute/zone.
REQUIRED FLAGS
Private cloud resource - private_cloud. The arguments in this group can be
used to specify the attributes of this 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 --private-cloud 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.
--private-cloud=PRIVATE_CLOUD
ID of the private cloud or fully qualified identifier for the private
cloud.
To set the private-cloud attribute:
▸ provide the argument --private-cloud on the command line.
This flag argument must be specified if any of the other arguments in
this group are specified.
--location=LOCATION
Location of the private cloud or cluster.
To set the location attribute:
▸ provide the argument --private-cloud on the command line with a
fully specified name;
▸ provide the argument --location on the command line;
▸ set the property 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.

View file

@ -0,0 +1,100 @@
NAME
gcloud vmware private-clouds logging-servers update - update a Google Cloud
VMware Engine logging-server
SYNOPSIS
gcloud vmware private-clouds logging-servers update
(LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD)
[--async] [--hostname=HOSTNAME] [--port=PORT] [--protocol=PROTOCOL]
[--source-type=SOURCE_TYPE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Update a Logging Server. Only source_type, hostname, protocol, port can be
updated.
EXAMPLES
To update a logging-server called my-logging-server in private cloud
my-private-cloud and zone us-west2-a to change ESXI source_type,
192.168.20.15 hostname UDP protocol and 514 port, run:
$ gcloud vmware private-clouds logging-servers update \
my-logging-server --location=us-west2-a --project=my-project \
--private-cloud=my-private-cloud --source-type=ESXI \
--hostname=192.168.20.15 --protocol=UDP --port=514
Or:
$ gcloud vmware private-clouds logging-servers update \
my-logging-server --private-cloud=my-private-cloud \
--source-type=ESXI --hostname=192.168.20.15 --protocol=UDP \
--port=514
In the second example, the project and location are taken from gcloud properties core/project and compute/zone.
POSITIONAL ARGUMENTS
Logging Server resource - logging_server. The arguments in this group can
be used to specify the attributes of this 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 logging_server 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.
LOGGING_SERVER
ID of the Logging Server or fully qualified identifier for the
Logging Server.
To set the logging-server attribute:
▸ provide the argument logging_server on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location of the private cloud or cluster.
To set the location attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --location on the command line;
▸ set the property compute/zone.
--private-cloud=PRIVATE_CLOUD
VMware Engine private cloud.
To set the private-cloud attribute:
▸ provide the argument logging_server on the command line with a
fully specified name;
▸ provide the argument --private-cloud on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete. The default is True. Enabled by default, use --no-async to
disable.
--hostname=HOSTNAME
Fully-qualified domain name (FQDN) or IP Address of the logging server.
--port=PORT
Port number at which the logging server receives logs.
--protocol=PROTOCOL
Defines possible protocols used to send logs to a logging server.
PROTOCOL must be one of: UDP, TCP.
--source-type=SOURCE_TYPE
The type of component that produces logs that will be forwarded to this
logging server. SOURCE_TYPE must be one of: VCSA, ESXI.
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.