2022-03-01 04:29:52 +00:00
|
|
|
NAME
|
|
|
|
|
gcloud beta debug snapshots wait - wait for debug snapshots on a Cloud
|
|
|
|
|
Debugger debug target (debuggee) to complete
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
gcloud beta debug snapshots wait [ID ...] [--all] [--all-users]
|
|
|
|
|
[--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)]
|
|
|
|
|
[--timeout=TIMEOUT; default="unlimited"] [--filter=EXPRESSION]
|
|
|
|
|
[--limit=LIMIT] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
2023-02-15 10:13:15 +00:00
|
|
|
(BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May
|
|
|
|
|
31, 2023.
|
|
|
|
|
|
|
|
|
|
See: https://cloud.google.com/debugger/docs/deprecations
|
|
|
|
|
|
|
|
|
|
gcloud beta debug snapshots wait is used to wait for one or more snapshots
|
|
|
|
|
on a Cloud Debugger debug target to complete. A snapshot is considered
|
|
|
|
|
completed either if there was an error setting the snapshot or if the
|
|
|
|
|
snapshot was hit on an instance of the debug target.
|
2022-03-01 04:29:52 +00:00
|
|
|
|
|
|
|
|
EXAMPLES
|
|
|
|
|
To wait for either of the snapshots with IDs of 'ID1' or 'ID2' of the debug
|
|
|
|
|
target (debuggee) to complete, run:
|
|
|
|
|
|
|
|
|
|
$ gcloud beta debug snapshots wait ID1 ID2 --target=<debuggee_id>
|
|
|
|
|
|
|
|
|
|
To wait for both of the snapshots with IDs 'ID1' and 'ID2' of the debug
|
|
|
|
|
target (debuggee) to complete, run:
|
|
|
|
|
|
|
|
|
|
$ gcloud beta debug snapshots wait ID1 ID2 --target=<debuggee_id> \
|
|
|
|
|
--all
|
|
|
|
|
|
|
|
|
|
To wait up to 30 seconds for the snapshot with ID 'ID1' of the debug target
|
|
|
|
|
(debuggee) to complete, run:
|
|
|
|
|
|
|
|
|
|
$ gcloud beta debug snapshots wait ID1 --target=<debuggee_id> \
|
|
|
|
|
--timeout=30
|
|
|
|
|
|
|
|
|
|
POSITIONAL ARGUMENTS
|
|
|
|
|
[ID ...]
|
|
|
|
|
Zero or more snapshot resource identifiers. The command will wait for
|
|
|
|
|
any of the specified snapshots to complete.
|
|
|
|
|
|
|
|
|
|
FLAGS
|
|
|
|
|
--all
|
|
|
|
|
If set, wait for all of the specified snapshots to complete, instead of
|
|
|
|
|
waiting for any one of them to complete.
|
|
|
|
|
|
|
|
|
|
--all-users
|
|
|
|
|
If set, wait for matching snapshots from all users, rather than only
|
|
|
|
|
the current user.
|
|
|
|
|
|
|
|
|
|
--location=LOCATION-REGEXP
|
|
|
|
|
A regular expression to match against snapshot locations. The command
|
|
|
|
|
will wait for any snapshots matching these criteria to complete. You
|
|
|
|
|
may specify --location multiple times.
|
|
|
|
|
|
|
|
|
|
EXAMPLE:
|
|
|
|
|
|
|
|
|
|
gcloud beta debug snapshots wait \
|
|
|
|
|
--location foo.py:[1-3] --location bar.py:3
|
|
|
|
|
|
|
|
|
|
--target=(ID|DESCRIPTION_REGEXP)
|
|
|
|
|
The debug target. It may be a target ID or name obtained from 'debug
|
|
|
|
|
targets list', or it may be a regular expression uniquely specifying a
|
|
|
|
|
debuggee based on its description or name. For App Engine projects, if
|
|
|
|
|
not specified, the default target is the most recent deployment of the
|
|
|
|
|
default module and version.
|
|
|
|
|
|
|
|
|
|
--timeout=TIMEOUT; default="unlimited"
|
|
|
|
|
Maximum number of seconds to wait for a snapshot to complete. By
|
|
|
|
|
default, wait indefinitely.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
--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.
|
|
|
|
|
|
|
|
|
|
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 beta and might change without notice. This
|
|
|
|
|
variant is also available:
|
|
|
|
|
|
|
|
|
|
$ gcloud debug snapshots wait
|
|
|
|
|
|
