1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
gcloud-help/gcloud/memorystore/instances/delete
2024-12-11 10:18:23 +00:00

88 lines
3.3 KiB
Text

NAME
gcloud memorystore instances delete - delete a Memorystore instance
SYNOPSIS
gcloud memorystore instances delete (INSTANCE : --location=LOCATION)
[--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Delete a Memorystore instance.
EXAMPLES
To delete Memorystore instance my-instance in project my-project and
location us-central1, run:
$ gcloud 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/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 instances delete
$ gcloud beta memorystore instances delete