imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 23:08:48 +00:00
Code Activity

gcloud: Thu Feb 20 10:40:27 UTC 2025

Browse source
This commit is contained in:
Automated 2025-02-20 10:40:27 +00:00
parent 44f319c56c
commit 8d1a988ab5
295 changed files with 11246 additions and 956 deletions
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/memorystore/help
View file

@ -18,6 +18,9 @@ GROUPS
instances
Manage Instance resources.
locations
Manage Memorystore for Valkey locations.
operations
Manage Memorystore operations.

94
gcloud/memorystore/instances/create
View file

@ -3,12 +3,14 @@ NAME
SYNOPSIS
gcloud memorystore instances create (INSTANCE : --location=LOCATION)
--psc-auto-connections=[network=NETWORK],[projectId=PROJECTID]
[--async] [--authorization-mode=AUTHORIZATION_MODE]
[--deletion-protection-enabled] [--engine-configs=[ENGINE_CONFIGS,...]]
[--deletion-protection-enabled] [--endpoints=[connections=CONNECTIONS]]
[--engine-configs=[ENGINE_CONFIGS,...]]
[--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] [--mode=MODE]
[--node-type=NODE_TYPE] [--replica-count=REPLICA_COUNT]
[--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT]
[--node-type=NODE_TYPE]
[--psc-auto-connections=[network=NETWORK],[projectId=PROJECTID]]
[--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID]
[--shard-count=SHARD_COUNT]
[--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE]
[--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC
--persistence-config-mode=PERSISTENCE_CONFIG_MODE
@ -76,31 +78,7 @@ POSITIONAL ARGUMENTS
specified name;
▸ provide the argument --location on the command line.
REQUIRED FLAGS
--psc-auto-connections=[network=NETWORK],[projectId=PROJECTID]
Required, User inputs and resource details of the auto-created PSC
connections.
network
The consumer network where the IP address resides, in the form of
projects/{project_id}/global/networks/{network_id}.
projectId
The consumer project_id where the forwarding rule is created from.
Shorthand Example:
--psc-auto-connections=network=string,projectId=string --psc-auto-connections=network=string,projectId=string
JSON Example:
--psc-auto-connections='[{"network": "string", "projectId": "string"}]'
File Example:
--psc-auto-connections=path_to_file.(yaml|json)
OPTIONAL FLAGS
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
@ -118,6 +96,38 @@ OPTIONAL FLAGS
--deletion-protection-enabled
If set to true deletion of the instance will fail.
--endpoints=[connections=CONNECTIONS]
Endpoints for the instance.
connections
A group of PSC connections. They are created in the same VPC
network, one for each service attachment in the cluster.
pscAutoConnection
Detailed information of a PSC connection that is created
through service connectivity automation.
network
The network where the PSC endpoints are created, in the
form of projects/{project_id}/global/networks/{network_id}.
projectId
The consumer project_id where PSC connections are
established. This should be the same project_id that the
instance is being created in.
Shorthand Example:
--endpoints=connections=[{pscAutoConnection={network=string,projectId=string}}] --endpoints=connections=[{pscAutoConnection={network=string,projectId=string}}]
JSON Example:
--endpoints='[{"connections": [{"pscAutoConnection": {"network": "string", "projectId": "string"}}]}]'
File Example:
--endpoints=path_to_file.(yaml|json)
--engine-configs=[ENGINE_CONFIGS,...]
User-provided engine configurations for the instance.
@ -172,6 +182,8 @@ OPTIONAL FLAGS
Instance is in cluster mode.
cluster-disabled
Cluster mode is disabled for the instance.
standalone
Deprecated: Use CLUSTER_DISABLED instead.
--node-type=NODE_TYPE
Machine type for individual nodes of the instance. NODE_TYPE must be
@ -186,6 +198,30 @@ OPTIONAL FLAGS
standard-small
Standard small.
--psc-auto-connections=[network=NETWORK],[projectId=PROJECTID]
User inputs and resource details of the auto-created PSC connections.
network
The network where the PSC endpoints are created, in the form of
projects/{project_id}/global/networks/{network_id}.
projectId
The consumer project_id where PSC connections are established. This
should be the same project_id that the instance is being created
in.
Shorthand Example:
--psc-auto-connections=network=string,projectId=string --psc-auto-connections=network=string,projectId=string
JSON Example:
--psc-auto-connections='[{"network": "string", "projectId": "string"}]'
File Example:
--psc-auto-connections=path_to_file.(yaml|json)
Arguments for the replica count.
--replica-count=REPLICA_COUNT

164
gcloud/memorystore/instances/update
View file

@ -4,13 +4,17 @@ NAME
SYNOPSIS
gcloud memorystore instances update (INSTANCE : --location=LOCATION)
[--async] [--[no-]deletion-protection-enabled]
[--async] [--[no-]deletion-protection-enabled] [--mode=MODE]
[--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID]
[--shard-count=SHARD_COUNT]
[--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC
--clear-persistence-config
--persistence-config-mode=PERSISTENCE_CONFIG_MODE
--rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD
--rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME]
[--endpoints=[connections=CONNECTIONS]
| --add-endpoints=[connections=CONNECTIONS] --clear-endpoints
| --remove-endpoints=[connections=CONNECTIONS]]
[--engine-configs=[ENGINE_CONFIGS,...]
| --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...]
--clear-engine-configs
@ -80,6 +84,16 @@ FLAGS
--deletion-protection-enabled to enable and
--no-deletion-protection-enabled to disable.
--mode=MODE
The mode config for the instance. MODE must be one of:
cluster
Instance is in cluster mode.
cluster-disabled
Cluster mode is disabled for the instance.
standalone
Deprecated: Use CLUSTER_DISABLED instead.
Arguments for the replica count.
--replica-count=REPLICA_COUNT
@ -122,6 +136,9 @@ FLAGS
with this configuration, but it's up to the kernel's exact
tuning.
--clear-persistence-config
Set instance.persistenceConfig back to default value.
--persistence-config-mode=PERSISTENCE_CONFIG_MODE
Current persistence mode. PERSISTENCE_CONFIG_MODE must be one of:
@ -152,6 +169,151 @@ FLAGS
future snapshots will be aligned. If not provided, the current time
will be used.
Update endpoints.
At most one of these can be specified:
--endpoints=[connections=CONNECTIONS]
Set endpoints to new value. Endpoints for the instance.
connections
A group of PSC connections. They are created in the same VPC
network, one for each service attachment in the cluster.
pscConnection
Detailed information of a PSC connection that is created by
the user.
forwardingRule
The URI of the consumer side forwarding rule. Format:
projects/{project}/regions/{region}/forwardingRules/{forwarding_rule}.
ipAddress
The IP allocated on the consumer network for the PSC
forwarding rule.
network
The consumer network where the IP address resides, in the
form of
projects/{project_id}/global/networks/{network_id}.
pscConnectionId
The PSC connection id of the forwarding rule connected to
the service attachment.
serviceAttachment
The service attachment which is the target of the PSC
connection, in the form of
projects/{project-id}/regions/{region}/serviceAttachments/{service-attachment-id}.
Shorthand Example:
--endpoints=connections=[{pscConnection={forwardingRule=string,ipAddress=string,network=string,pscConnectionId=string,serviceAttachment=string}}] --endpoints=connections=[{pscConnection={forwardingRule=string,ipAddress=string,network=string,pscConnectionId=string,serviceAttachment=string}}]
JSON Example:
--endpoints='[{"connections": [{"pscConnection": {"forwardingRule": "string", "ipAddress": "string", "network": "string", "pscConnectionId": "string", "serviceAttachment": "string"}}]}]'
File Example:
--endpoints=path_to_file.(yaml|json)
--add-endpoints=[connections=CONNECTIONS]
Add new value to endpoints list. Endpoints for the instance.
connections
A group of PSC connections. They are created in the same VPC
network, one for each service attachment in the cluster.
pscConnection
Detailed information of a PSC connection that is created by
the user.
forwardingRule
The URI of the consumer side forwarding rule. Format:
projects/{project}/regions/{region}/forwardingRules/{forwarding_rule}.
ipAddress
The IP allocated on the consumer network for the PSC
forwarding rule.
network
The consumer network where the IP address resides, in the
form of
projects/{project_id}/global/networks/{network_id}.
pscConnectionId
The PSC connection id of the forwarding rule connected to
the service attachment.
serviceAttachment
The service attachment which is the target of the PSC
connection, in the form of
projects/{project-id}/regions/{region}/serviceAttachments/{service-attachment-id}.
Shorthand Example:
--add-endpoints=connections=[{pscConnection={forwardingRule=string,ipAddress=string,network=string,pscConnectionId=string,serviceAttachment=string}}] --add-endpoints=connections=[{pscConnection={forwardingRule=string,ipAddress=string,network=string,pscConnectionId=string,serviceAttachment=string}}]
JSON Example:
--add-endpoints='[{"connections": [{"pscConnection": {"forwardingRule": "string", "ipAddress": "string", "network": "string", "pscConnectionId": "string", "serviceAttachment": "string"}}]}]'
File Example:
--add-endpoints=path_to_file.(yaml|json)
At most one of these can be specified:
--clear-endpoints
Clear endpoints value and set to empty list.
--remove-endpoints=[connections=CONNECTIONS]
Remove existing value from endpoints list. Endpoints for the
instance.
connections
A group of PSC connections. They are created in the same VPC
network, one for each service attachment in the cluster.
pscConnection
Detailed information of a PSC connection that is created by
the user.
forwardingRule
The URI of the consumer side forwarding rule. Format:
projects/{project}/regions/{region}/forwardingRules/{forwarding_rule}.
ipAddress
The IP allocated on the consumer network for the PSC
forwarding rule.
network
The consumer network where the IP address resides, in
the form of
projects/{project_id}/global/networks/{network_id}.
pscConnectionId
The PSC connection id of the forwarding rule connected
to the service attachment.
serviceAttachment
The service attachment which is the target of the PSC
connection, in the form of
projects/{project-id}/regions/{region}/serviceAttachments/{service-attachment-id}.
Shorthand Example:
--remove-endpoints=connections=[{pscConnection={forwardingRule=string,ipAddress=string,network=string,pscConnectionId=string,serviceAttachment=string}}] --remove-endpoints=connections=[{pscConnection={forwardingRule=string,ipAddress=string,network=string,pscConnectionId=string,serviceAttachment=string}}]
JSON Example:
--remove-endpoints='[{"connections": [{"pscConnection": {"forwardingRule": "string", "ipAddress": "string", "network": "string", "pscConnectionId": "string", "serviceAttachment": "string"}}]}]'
File Example:
--remove-endpoints=path_to_file.(yaml|json)
Update engine_configs.
At most one of these can be specified:

60
gcloud/memorystore/locations/describe Normal file
View file

@ -0,0 +1,60 @@
NAME
gcloud memorystore locations describe - show metadata for a Memorystore for
Valkey location
SYNOPSIS
gcloud memorystore locations describe LOCATION [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Display all metadata associated with a Memorystore for Valkey location
given a valid location name.
This command can fail for the following reasons:
▪ The location specified does not exist.
▪ The active account does not have permission to access the given
location.
EXAMPLES
To display the metadata for the location us-central1, run:
$ gcloud memorystore locations describe us-central1
POSITIONAL ARGUMENTS
Location resource - Arguments and flags that specify the Memorystore for
Valkey location you want to describe. 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 location on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
LOCATION
ID of the location or fully qualified identifier for the location.
To set the location attribute:
▸ provide the argument location 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.
API REFERENCE
This command uses the memorystore/v1 API. The full documentation for this
API can be found at: https://cloud.google.com/memorystore/
NOTES
These variants are also available:
$ gcloud alpha memorystore locations describe
$ gcloud beta memorystore locations describe

30
gcloud/memorystore/locations/help Normal file
View file

@ -0,0 +1,30 @@
NAME
gcloud memorystore locations - manage Memorystore for Valkey locations
SYNOPSIS
gcloud memorystore locations COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Manage Memorystore for Valkey locations.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Show metadata for a Memorystore for Valkey location.
list
List Memorystore for Valkey locations.
NOTES
These variants are also available:
$ gcloud alpha memorystore locations
$ gcloud beta memorystore locations

68
gcloud/memorystore/locations/list Normal file
View file

@ -0,0 +1,68 @@
NAME
gcloud memorystore locations list - list Memorystore for Valkey locations
SYNOPSIS
gcloud memorystore locations list [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all locations where Memorystore for Valkey API is available.
EXAMPLES
To list all the locations where Memorystore for Valkey instances can be
created, run:
$ gcloud memorystore locations list
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.
API REFERENCE
This command uses the memorystore/v1 API. The full documentation for this
API can be found at: https://cloud.google.com/memorystore/
NOTES
These variants are also available:
$ gcloud alpha memorystore locations list
$ gcloud beta memorystore locations list