1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 12:22:03 +00:00

gcloud: Wed Aug 28 09:41:07 UTC 2024

This commit is contained in:
Automated 2024-08-28 09:41:07 +00:00
parent ed5fe34b64
commit afbe8a5afb
256 changed files with 8602 additions and 358 deletions

View file

@ -0,0 +1,297 @@
NAME
gcloud beta memorystore instances create - create a Memorystore instance
SYNOPSIS
gcloud beta memorystore instances create (INSTANCE : --location=LOCATION)
--psc-auto-connections=[network=NETWORK],[projectId=PROJECTID]
--shard-count=SHARD_COUNT [--async]
[--authorization-mode=AUTHORIZATION_MODE]
[--deletion-protection-enabled] [--engine-configs=[ENGINE_CONFIGS,...]]
[--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]]
[--node-type=NODE_TYPE] [--replica-count=REPLICA_COUNT]
[--request-id=REQUEST_ID]
[--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE]
[--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC
--persistence-config-mode=PERSISTENCE_CONFIG_MODE
--rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD
--rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME]
[--zone-distribution-config=ZONE_DISTRIBUTION_CONFIG
--zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a Memorystore instance.
A service connection policy for service class gcp-memorystore must already
exist for the location and network. Refer to creation prerequisites
(https://cloud.google.com/memorystore/docs/valkey/networking#prerequisites_required_before_creating_an_instance)
for more details.
EXAMPLES
To create a three shard Memorystore instance my-instance in project
my-project and location us-central1, run:
$ gcloud beta memorystore instances create my-instance \
--project=my-project --location=us-central1 --shard-count=3 \
--psc-auto-connections="network=NETWORK,projectId=PROJECT_ID"
To create a three shard Memorystore instance my-instance in project
my-project, location us-central1, with one replica per shard, and TLS
enabled, run:
$ gcloud beta memorystore instances create my-instance \
--project=my-project --location=us-central1 --shard-count=3 \
--psc-auto-connections="network=NETWORK,projectId=PROJECT_ID" \
--transit-encryption-mode=server-authentication \
--replica-count=1
POSITIONAL ARGUMENTS
Instance resource - Identifier. Unique name of the instance. Format:
projects/{project}/locations/{location}/instances/{instance} 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 instance 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.
INSTANCE
ID of the instance or fully qualified identifier for the instance.
To set the instance attribute:
▸ provide the argument instance on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location id of the instance resource.
To set the location attribute:
▸ provide the argument instance on the command line with a fully
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)
--shard-count=SHARD_COUNT
Number of shards for the instance.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--authorization-mode=AUTHORIZATION_MODE
Authorization mode of the instance. AUTHORIZATION_MODE must be one of:
auth-disabled
Authorization disabled.
iam-auth
IAM basic authorization.
Arguments for the deletion protection enabled.
--deletion-protection-enabled
If set to true deletion of the instance will fail.
--engine-configs=[ENGINE_CONFIGS,...]
User-provided engine configurations for the instance.
KEY
Sets KEY value.
VALUE
Sets VALUE value.
Shorthand Example:
--engine-configs=string=string
JSON Example:
--engine-configs='{"string": "string"}'
File Example:
--engine-configs=path_to_file.(yaml|json)
--engine-version=ENGINE_VERSION
Engine version of the instance.
--labels=[LABELS,...]
Labels to represent user-provided metadata.
KEY
Keys must start with a lowercase character and contain only hyphens
(-), underscores (_), lowercase characters, and numbers.
VALUE
Values must contain only hyphens (-), underscores (_), lowercase
characters, and numbers.
Shorthand Example:
--labels=string=string
JSON Example:
--labels='{"string": "string"}'
File Example:
--labels=path_to_file.(yaml|json)
--node-type=NODE_TYPE
Machine type for individual nodes of the instance. NODE_TYPE must be
one of:
highmem-medium
High memory medium.
highmem-xlarge
High memory extra large.
shared-core-nano
Shared core nano.
standard-small
Standard small.
Arguments for the replica count.
--replica-count=REPLICA_COUNT
Number of replica nodes per shard. If omitted the default is 0
replicas.
--request-id=REQUEST_ID
An optional request ID to identify requests. Specify a unique request
ID so that if you must retry your request, the server will know to
ignore the request if it has already been completed. The server will
guarantee that for at least 60 minutes since the first request.
For example, consider a situation where you make an initial request and
the request times out. If you make the request again with the same
request ID, the server can check if original operation with the same
request ID was received, and if so, will ignore the second request.
This prevents clients from accidentally creating duplicate commitments.
The request ID must be a valid UUID with the exception that zero UUID
is not supported (00000000-0000-0000-0000-000000000000).
--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE
In-transit encryption mode of the instance. TRANSIT_ENCRYPTION_MODE
must be one of:
server-authentication
Server-managed encryption is used for in-transit encryption.
transit-encryption-disabled
In-transit encryption is disabled.
Represents persistence configuration for a instance.
Configuration for AOF based persistence.
--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC
The fsync mode. AOF_CONFIG_APPEND_FSYNC must be one of:
always
Fsync every time new write commands are appended to the AOF.
The best data loss protection at the cost of performance.
every-sec
Fsync every second. You may lose 1 second of data if there is a
disaster.
never
Never fsync. Normally Linux will flush data every 30 seconds
with this configuration, but it's up to the kernel's exact
tuning.
--persistence-config-mode=PERSISTENCE_CONFIG_MODE
Current persistence mode. PERSISTENCE_CONFIG_MODE must be one of:
aof
AOF based persistence is enabled.
disabled
Persistence is disabled, and any snapshot data is deleted.
rdb
RDB based persistence is enabled.
Configuration for RDB based persistence.
--rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD
Period between RDB snapshots. RDB_CONFIG_SNAPSHOT_PERIOD must be
one of:
one-hour
One hour.
six-hours
Six hours.
twelve-hours
Twelve hours.
twenty-four-hours
Twenty four hours.
--rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME
Time that the first snapshot was/will be attempted, and to which
future snapshots will be aligned. If not provided, the current time
will be used.
Zone distribution configuration for allocation of instance resources.
--zone-distribution-config=ZONE_DISTRIBUTION_CONFIG
Defines zone where all resources will be allocated with SINGLE_ZONE
mode. Ignored for MULTI_ZONE mode.
--zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE
Current zone distribution mode. Defaults to MULTI_ZONE.
ZONE_DISTRIBUTION_CONFIG_MODE must be one of:
multi-zone
Distribute resources across 3 zones picked at random within the
region.
single-zone
Provision resources in a single zone. Zone field must be
specified.
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/v1beta API. The full documentation for
this API can be found at: https://cloud.google.com/memorystore/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memorystore instances create

View file

@ -0,0 +1,87 @@
NAME
gcloud beta memorystore instances delete - delete a Memorystore instance
SYNOPSIS
gcloud beta memorystore instances delete (INSTANCE : --location=LOCATION)
[--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Delete a Memorystore instance.
EXAMPLES
To delete Memorystore instance my-instance in project my-project and
location us-central1, run:
$ gcloud beta memorystore instances delete my-instance \
--project=my-project --location=us-central1
POSITIONAL ARGUMENTS
Instance resource - The name of the instance to delete. Format:
projects/{project}/locations/{location}/instances/{instance} 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 instance 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.
INSTANCE
ID of the instance or fully qualified identifier for the instance.
To set the instance attribute:
▸ provide the argument instance on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location id of the instance resource.
To set the location attribute:
▸ provide the argument instance on the command line with a fully
specified name;
▸ provide the argument --location on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--request-id=REQUEST_ID
An optional request ID to identify requests. Specify a unique request
ID so that if you must retry your request, the server will know to
ignore the request if it has already been completed. The server will
guarantee that for at least 60 minutes after the first request.
For example, consider a situation where you make an initial request and
the request times out. If you make the request again with the same
request ID, the server can check if original operation with the same
request ID was received, and if so, will ignore the second request.
This prevents clients from accidentally creating duplicate commitments.
The request ID must be a valid UUID with the exception that zero UUID
is not supported (00000000-0000-0000-0000-000000000000).
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/v1beta API. The full documentation for
this API can be found at: https://cloud.google.com/memorystore/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memorystore instances delete

View file

@ -0,0 +1,68 @@
NAME
gcloud beta memorystore instances describe - get details of a Memorystore
instance
SYNOPSIS
gcloud beta memorystore instances describe (INSTANCE : --location=LOCATION)
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get details of a Memorystore instance.
EXAMPLES
To get the details of Memorystore instance my-instance in project
my-project and location us-central, run:
$ gcloud beta memorystore instances describe my-instance \
--project=my-project --location=us-central1
POSITIONAL ARGUMENTS
Instance resource - The name of the instance to retrieve. Format:
projects/{project}/locations/{location}/instances/{instance} 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 instance 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.
INSTANCE
ID of the instance or fully qualified identifier for the instance.
To set the instance attribute:
▸ provide the argument instance on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location id of the instance resource.
To set the location attribute:
▸ provide the argument instance on the command line with a fully
specified name;
▸ 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/v1beta API. The full documentation for
this API can be found at: https://cloud.google.com/memorystore/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memorystore instances describe

View file

@ -0,0 +1,68 @@
NAME
gcloud beta memorystore instances get-certificate-authority - get
certificate authority details of a Memorystore instance
SYNOPSIS
gcloud beta memorystore instances get-certificate-authority
(INSTANCE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Get certificate authority details of a Memorystore instance.
EXAMPLES
To get the certificate authority for instance my-instance in project
my-project and location us-central1, run:
$ gcloud beta memorystore instances get-certificate-authority \
my-instance --project=my-project --location=us-central1
POSITIONAL ARGUMENTS
Instance resource - The name of the Memorystore instance. Format:
projects/{project}/locations/{location}/instances/{instance} 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 instance 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.
INSTANCE
ID of the instance or fully qualified identifier for the instance.
To set the instance attribute:
▸ provide the argument instance on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location ID of the instance resource.
To set the location attribute:
▸ provide the argument instance on the command line with a fully
specified name;
▸ 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/v1beta API. The full documentation for
this API can be found at: https://cloud.google.com/memorystore/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memorystore instances get-certificate-authority

View file

@ -0,0 +1,42 @@
NAME
gcloud beta memorystore instances - manage Instance resources
SYNOPSIS
gcloud beta memorystore instances COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Manage Instance resources.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
create
(BETA) Create a Memorystore instance.
delete
(BETA) Delete a Memorystore instance.
describe
(BETA) Get details of a Memorystore instance.
get-certificate-authority
(BETA) Get certificate authority details of a Memorystore instance.
list
(BETA) List all Memorystore instances in a specified project and
location.
update
(BETA) Update the configuration of a Memorystore instance.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memorystore instances

View file

@ -0,0 +1,89 @@
NAME
gcloud beta memorystore instances list - list all Memorystore instances in
a specified project and location
SYNOPSIS
gcloud beta memorystore instances list --location=LOCATION
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List all Memorystore instances in a specified project and location.
EXAMPLES
To list all Memorystore instances in project my-project and location
us-central, run:
$ gcloud beta memorystore instances list --project=my-project \
--location=us-central1
REQUIRED FLAGS
Location resource - The parent to list instances from. Format:
projects/{project}/locations/{location} 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=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.
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/v1beta API. The full documentation for
this API can be found at: https://cloud.google.com/memorystore/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memorystore instances list

View file

@ -0,0 +1,285 @@
NAME
gcloud beta memorystore instances update - update the configuration of a
Memorystore instance
SYNOPSIS
gcloud beta memorystore instances update (INSTANCE : --location=LOCATION)
[--async] [--deletion-protection-enabled]
[--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID]
[--shard-count=SHARD_COUNT]
[--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC
--persistence-config-mode=PERSISTENCE_CONFIG_MODE
--rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD
--rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME]
[--engine-configs=[ENGINE_CONFIGS,...]
| --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...]
--clear-engine-configs
| --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...]]
[--labels=[LABELS,...]
| --update-labels=[UPDATE_LABELS,...] --clear-labels
| --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update the configuration of a Memorystore instance.
EXAMPLES
To update Memorystore instance my-instance in project my-project and
location us-central1 to six shards, run:
$ gcloud beta memorystore instances update `my-instance` \
--project=my-project --location=us-central1 --shard-count=6
To update Memorystore instance my-instance in project my-project and
location us-central1 to use a maxmemory-policy of allkeys-lru, run:
$ gcloud beta memorystore instances update `my-instance` \
--project=my-project --location=us-central1 \
--update-engine-configs=maxmemory-policy=allkeys-lru
POSITIONAL ARGUMENTS
Instance resource - Identifier. Unique name of the instance. Format:
projects/{project}/locations/{location}/instances/{instance} 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 instance 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.
INSTANCE
ID of the instance or fully qualified identifier for the instance.
To set the instance attribute:
▸ provide the argument instance on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
The location id of the instance resource.
To set the location attribute:
▸ provide the argument instance on the command line with a fully
specified name;
▸ provide the argument --location on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
Arguments for the deletion protection enabled.
--deletion-protection-enabled
If set to true deletion of the instance will fail.
Arguments for the replica count.
--replica-count=REPLICA_COUNT
Number of replica nodes per shard. If omitted the default is 0
replicas.
--request-id=REQUEST_ID
An optional request ID to identify requests. Specify a unique request
ID so that if you must retry your request, the server will know to
ignore the request if it has already been completed. The server will
guarantee that for at least 60 minutes since the first request.
For example, consider a situation where you make an initial request and
the request times out. If you make the request again with the same
request ID, the server can check if original operation with the same
request ID was received, and if so, will ignore the second request.
This prevents clients from accidentally creating duplicate commitments.
The request ID must be a valid UUID with the exception that zero UUID
is not supported (00000000-0000-0000-0000-000000000000).
--shard-count=SHARD_COUNT
Number of shards for the instance.
Represents persistence configuration for a instance.
Configuration for AOF based persistence.
--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC
The fsync mode. AOF_CONFIG_APPEND_FSYNC must be one of:
always
Fsync every time new write commands are appended to the AOF.
The best data loss protection at the cost of performance.
every-sec
Fsync every second. You may lose 1 second of data if there is a
disaster.
never
Never fsync. Normally Linux will flush data every 30 seconds
with this configuration, but it's up to the kernel's exact
tuning.
--persistence-config-mode=PERSISTENCE_CONFIG_MODE
Current persistence mode. PERSISTENCE_CONFIG_MODE must be one of:
aof
AOF based persistence is enabled.
disabled
Persistence is disabled, and any snapshot data is deleted.
rdb
RDB based persistence is enabled.
Configuration for RDB based persistence.
--rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD
Period between RDB snapshots. RDB_CONFIG_SNAPSHOT_PERIOD must be
one of:
one-hour
One hour.
six-hours
Six hours.
twelve-hours
Twelve hours.
twenty-four-hours
Twenty four hours.
--rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME
Time that the first snapshot was/will be attempted, and to which
future snapshots will be aligned. If not provided, the current time
will be used.
Update engine_configs.
At most one of these can be specified:
--engine-configs=[ENGINE_CONFIGS,...]
Set engine_configs to new value. User-provided engine configurations
for the instance.
KEY
Sets KEY value.
VALUE
Sets VALUE value.
Shorthand Example:
--engine-configs=string=string
JSON Example:
--engine-configs='{"string": "string"}'
File Example:
--engine-configs=path_to_file.(yaml|json)
--update-engine-configs=[UPDATE_ENGINE_CONFIGS,...]
Update engine_configs value or add key value pair. User-provided
engine configurations for the instance.
KEY
Sets KEY value.
VALUE
Sets VALUE value.
Shorthand Example:
--update-engine-configs=string=string
JSON Example:
--update-engine-configs='{"string": "string"}'
File Example:
--update-engine-configs=path_to_file.(yaml|json)
At most one of these can be specified:
--clear-engine-configs
Clear engine_configs value and set to empty map.
--remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...]
Remove existing value from map engine_configs.
Update labels.
At most one of these can be specified:
--labels=[LABELS,...]
Set labels to new value. Labels to represent user-provided metadata.
KEY
Keys must start with a lowercase character and contain only
hyphens (-), underscores (_), lowercase characters, and numbers.
VALUE
Values must contain only hyphens (-), underscores (_), lowercase
characters, and numbers.
Shorthand Example:
--labels=string=string
JSON Example:
--labels='{"string": "string"}'
File Example:
--labels=path_to_file.(yaml|json)
--update-labels=[UPDATE_LABELS,...]
Update labels value or add key value pair. Labels to represent
user-provided metadata.
KEY
Keys must start with a lowercase character and contain only
hyphens (-), underscores (_), lowercase characters, and numbers.
VALUE
Values must contain only hyphens (-), underscores (_), lowercase
characters, and numbers.
Shorthand Example:
--update-labels=string=string
JSON Example:
--update-labels='{"string": "string"}'
File Example:
--update-labels=path_to_file.(yaml|json)
At most one of these can be specified:
--clear-labels
Clear labels value and set to empty map.
--remove-labels=[__REMOVE_LABELS,...]
Remove existing value from map labels.
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/v1beta API. The full documentation for
this API can be found at: https://cloud.google.com/memorystore/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memorystore instances update