# Snapshot Debugger
The Snapshot Debugger lets you inspect the state of a running cloud
application, at any code location, without stopping or slowing it down. It’s not
your traditional process debugger but rather an always on, whole app debugger
taking snapshots from any instance of the app.
You can use the Snapshot Debugger with any deployment of your application,
including test, development, and production. The debugger typically adds less
than 10ms to the request latency only when the application state is captured. In
most cases, this isn’t noticeable by users.
## Project Status: Archived
This project has been archived and is no longer supported. There will be no
further bug fixes or security patches. The repository can be forked by users
if they want to maintain it going forward.
This OSS solution provides an alternative to Cloud Debugger. Cloud Debugger was
deprecated on May 16, 2022 and the service was shut down on May 31, 2023
## Limitations
* Python 2.7 is not supported
## CLI Command Reference
See
[COMMAND_REFERENCE.md](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/snapshot_dbg_cli/COMMAND_REFERENCE.md).
## Installing the Snapshot Debugger CLI
Install the debugger CLI in your local environment, or in your Cloud Shell
$HOME directory. See [Using Cloud
Shell](https://cloud.google.com/shell/docs/using-cloud-shell) for information on
using Cloud Shell.
```
python3 -m pip install snapshot-dbg-cli
```
> **Note**: When using the Snapshot Debugger in Cloud Shell you will be asked to
Authorize using your account credentials.
## Running the Snapshot Debugger CLI
There are two options to run the CLI once the pip install has been completed.
### Option 1: Use the installed script
As part of the pip install process, a script, `snapshot-dbg-cli` will be
installed which can be used to run the CLI.
Example running the `list_debuggees` command:
```
snapshot-dbg-cli list_debuggees
```
> **NOTE**: To run the script this way from any directory, you must ensure the
script's install directory is in your PATH. Pip should emit a warning if the
install location is not in the PATH, and also provide the install location in
this case, so that you can add it to your PATH.
### Option 2: Run the package directly
Example running the `list_debuggees` command:
```
python3 -m snapshot_dbg_cli list_debuggees
```
## Before you begin
### Ensure you have the proper permissions
To complete the setup you’ll need to have the following permissions in your
Google Cloud project. If you are an `Owner` or `Editor` of the Google Cloud
project, then you have these permissions.
* firebase.projects.create
* firebase.projects.update,
* firebasedatabase.instances.create
* firebasedatabase.instances.get
* resourcemanager.projects.get
* serviceusage.services.enable
* serviceusage.services.get
For more information on permissions and roles in Google projects, read
[Understanding
roles](https://cloud.google.com/iam/docs/understanding-roles#firebase-roles)
### Using Snapshot Debugger in Cloud Shell
Snapshot Debugger requires Python 3.6 or above and the `gcloud` CLI. If you are
working in Cloud Shell, you already have Python and `gcloud` installed.
In addition, the environment should already configured correctly by default. You
can verify this by running the following commands:
1. `gcloud config get-value project`
2. `gcloud config get-value account`
> **NOTE**: When running the cli, you may encounter a popup warning you that
`gcloud is requesting your credentials to make a GCP API call`. You'll need to
click `AUTHORIZE` to proceed.
### Using Snapshot Debugger outside of Cloud Shell
#### Ensure you have Python 3.6 or above installed
The Snapshot Debugger CLI requires [Python](https://www.python.org/downloads/)
3.6 or newer.
#### Install Google Cloud `gcloud` CLI
The Snapshot Debugger CLI depends on the `gcloud` CLI. To install the `gcloud`
CLI, follow these [instructions](https://cloud.google.com/sdk/docs/install). If
you already have the `gcloud` CLI installed, run `gcloud components update` to
update all of your installed components to the latest version.
#### Set up the environment
1. Run `gcloud auth login`, be sure to use the account that has permissions on
the Google Cloud project you are working on.
2. Run `gcloud config set project PROJECT_ID`. Where PROJECT_ID is the project
you want to use. The Snapshot Debugger CLI always acts on the current
`gcloud` configured project.
## Enable Firebase for your Google Cloud Project
The Snapshot Debugger CLI and agents use a Firebase Realtime Database (RTDB) to
communicate.
If you already use Firebase in your project, skip to the [Set up the Firebase
RTDB](#set-up-the-firebase-rtdb) section.
1. Add Firebase to your project:
https://console.firebase.google.com/?dlAction=MigrateCloudProject&cloudProjectNumber=PROJECT_ID
Where PROJECT_ID is your project ID
2. Select your
[Project ID](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects)
and click **Continue**. If you have billing enabled in your project, the
pay-as-you-go Blaze plan is selected, otherwise the free Spark plan is
selected. If you have billing enabled and want to use the free Spark plan,
set up a new project without billing enabled.
Note: The Snapshot Debugger uses the Firebase RTDB service. Most users' usage
will be low enough to remain under the [free usage
limits](https://firebase.google.com/pricing?).
3. If you are using the pay-as-you-go Blaze plan, click **Confirm plan**. You
are not prompted to confirm if you are on the free Spark plan.
4. Read the information under **A Few things to remember when adding Firebase to
a Google Cloud project** then click **Continue**.
5. Toggle the **enable analytics** option to enable or disable Google Analytics
for Firebase. Google Analytics isn't required for Debugger use.
6. Click **Continue**.
7. Click **Get Started**.
8. Click on your project.
### Set up the Firebase RTDB
The instructions are slightly different depending on whether you are on the
Spark or Blaze billing plan. Follow the steps in the following section for the
plan you have.
You can check what billing plan is in effect for your project on the Firebase Usage & Billing page:
https://console.firebase.google.com/project/PROJECT_ID/usage/details
Where PROJECT_ID is your project ID
#### Blaze plan RTDB setup
This will instruct the debugger CLI to create and use a database with the name
`PROJECT_ID-cdbg`
1. Run `snapshot-dbg-cli init`.
2. The output resembles the following:
```
Project 'test-proj' is successfully configured with the Firebase Realtime
Database for use by Snapshot Debugger.
The full database information is below. If you have specified a custom database
ID the url below is the one you'll need to specify when using the other cli
commands.
name: projects/23498723497/locations/us-central1/instances/test-proj-cdbg
project: projects/23498723497
database url: https://test-proj-cdbg.firebaseio.com
type: USER_DATABASE
state: ACTIVE
```
Note: The information printed by the `init` command can be accessed from within
your Firebase project. It’s safe to run the `snapshot-dbg-cli init` command
multiple times to view this information.
#### Spark plan RTDB setup
This will instruct the CLI to create and use a database with the name
`PROJECT_ID-default-rtdb`. It will only be created if it does not currently
exist.
1. Run `snapshot-dbg-cli init --use-default-rtdb`
2. The output resembles the following:
```
Project 'test-proj' is successfully configured with the Firebase Realtime
Database for use by Snapshot Debugger.
The full database information is below. If you have specified a custom database
ID the url below is the one you'll need to specify when using the other cli
commands.
name: projects/23498723497/locations/us-central1/instances/default
project: projects/23498723497
database url: https://test-proj-default-rtdb.firebaseio.com
type: USER_DATABASE
state: ACTIVE
```
Note: The information printed by the `init` command can be accessed from within
your Firebase project. It’s safe to run the `snapshot-dbg-cli init
--use-default-rtdb` command multiple times to view this information.
#### Setting up Firebase RTDB in other regions
By default, `snapshot-dbg-cli init` will create a Firebase Realtime Database in
`us-central1`. It is possible to create and use a database in any region
supported by Firebase Realtime Database. See
[supported RTDB locations][rtdb_locations].
Setting up your database in a non-default region comes with some trade-offs:
* As a positive, you get to control where your snapshot data will be stored.
This may be important for compliance reasons.
* As a negative, the vsCode extension and agents will be unable to
automatically find the database. The database URL will need to be provided
explicitly via configuration, see the following for details:
* [Configuring the Java Agent][java_agent_config]
* [Configuring the Python Agent][python_agent_config]
* [Configuring the Node.js Agent][nodejs_agent_config]
* [Configuring the VsCode Extension][extension_config]
You can set up your database in a non-default location as follows:
```
snapshot-dbg-cli init --location={YOUR_LOCATION}
```
For example, you may want to set up your database in Belgium, and so would run
```snapshot-dbg-cli init --location=europe-west1```
Make note of the database URL provided in the command output; you will need to
provide this to your debug agent(s) and the vsCode plugin.
[rtdb_locations]: https://firebase.google.com/docs/projects/locations#rtdb-locations
[java_agent_config]: https://github.com/GoogleCloudPlatform/cloud-debug-java/blob/main/README.md#configuring-the-firebase-realtime-database-url
[python_agent_config]: https://github.com/GoogleCloudPlatform/cloud-debug-python/blob/main/README.md#flag-reference
[nodejs_agent_config]: https://github.com/googleapis/cloud-debug-nodejs/blob/main/README.md#debugger-agent-settings
[extension_config]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/snapshot_dbg_extension/README.md#configuration
## Set up Snapshot Debugger in your Google Cloud project
### Working Samples
Working examples of using the Snapshot Debugger with Java, Python and Node.js
applications across different Google Cloud environments can be found in:
* [snapshot-debugger/samples][samples]
[samples]: https://github.com/GoogleCloudPlatform/snapshot-debugger/tree/main/samples
[notes-local]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/samples/README.md#notes-on-running-locally
### Agent Documentation
See the following for agent specific documentation:
* [Java](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/java.md)
* [Node.js](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/node-js.md)
* [Python](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/python.md)
## Example workflow
You create a breakpoint (snapshot or logpoint) on debuggees. Debuggees represent
instances of the running application. In general all instances of the same
version of the application will have the same debuggee ID, and breakpoints set
on a debuggee will be installed on all running instances of it.
### List Debuggees
Run the following command
```
snapshot-dbg-cli list_debuggees --include-inactive
```
The output resembles the following:
```
Name ID Description Last Active Status
------------- ---------- ---------------------------------------- -------------------- --------
test-app - v2 d-8dd7f149 node index.js module:test-app version:v2 2022-12-16T21:45:07Z ACTIVE
test-app - v1 d-24abc4f1 node index.js module:test-app version:v1 2022-10-16T21:45:07Z INACTIVE
```
### Set Snapshots
Snapshots capture local variables and the call stack at a specific line location
in your app's source code. You can specify certain conditions and locations to
return a snapshot of your app's data, and view it in detail to debug your app.
Set snapshots with the following command:
```
snapshot-dbg-cli set_snapshot index.js:21 --debuggee-id d-8dd7f149
```
Where:
* `index.js:21` is the `file:line` for the snapshot
* `d-8dd7f149` is the debuggee ID
#### Snapshot conditions (optional)
A snapshot condition is a simple expression in the app's language that must
evaluate to true for the snapshot to be taken. Snapshot conditions are evaluated
each time the line is executed, by any instance, until the condition evaluates
to true or the snapshot times out.
Use of snapshot conditions is optional.
The condition is a full boolean expression that can include logical operators.
Conditions are specified using the `--condition` flag of the `set_snapshots`
command.
Example:
```
snapshot-dbg-cli set_snapshot index.js:26 --debuggee-id d-8dd7f149 --condition="ultimateAnswer <= 42 && foo==bar"
```
You can use the following language features to express conditions:
##### Java
Most Java expressions are supported, including:
* Local variables: `a == 8`.
* Numerical and boolean operations: `x + y < 20`.
* Instance and static fields: `this.counter == 20`, `this.myObj.isShutdown`,
`myStatic`, or `com.mycompany.MyClass.staticMember`.
* String comparisons with the equality operator: `myString == "abc"`.
* Function calls. Only read-only functions can be used. For example,
`StringBuilder.indexOf()` is supported, but `StringBuilder.append()` is not.
* Type casting, with fully qualified types: `((com.myprod.ClassImpl)
myInterface).internalField`
The following language features are *not* supported:
* Unboxing of numeric types, such as `Integer`; use `myInteger.value` instead.
##### Python
Most Python expressions are supported, including:
* Reading local and global variables.
* Reading from arrays, lists, slices, dictionaries and objects.
* Calling simple methods.
The following language features are not supported:
* Calling functions that allocate new objects or use complex constructs.
* Creating new objects inside the expression.
##### Node.js
Most Javascript expressions are supported, with the following caveat:
Expressions that may have static side effects are disallowed. The debug agent
ensures all conditions and watchpoints you add are read-only and have no side
effects, however, it doesn’t catch expressions that have dynamic side-effects.
For example, `o.f` looks like a property access, but dynamically, it may end up
calling a getter function. The debugger presently doesn't detect such
dynamic-side effects.
#### Snapshot expressions (optional)
Snapshot Debugger's Expressions feature allows you to evaluate complex
expressions or traverse object hierarchies when a snapshot is taken. Expressions
support the same language features as [snapshot conditions](#snapshot-conditions-optional), described above.
Use of expressions is optional.
Typical uses for expressions are:
* To view static or global variables that are not part of the local variable
set.
* To easily view deeply nested member variables.
* To avoid repetitive mathematical calculations. For example, calculating a
duration in seconds with `(endTimeMillis - startTimeMillis) / 1000.0`.
Expressions are specified using the --expression flag of the set_snapshots
command.
Example:
```
snapshot-dbg-cli set_snapshot index.js:26 --debuggee-id d-8dd7f149 --expression="histogram.length"
```
### List snapshots
List snapshots with the following command:
```
snapshot-dbg-cli list_snapshots --debuggee-id d-8dd7f149 --include-inactive
```
Where:
* `d-8dd7f149` is the debuggee ID
The output resembles the following:
```
Status Location Condition CompletedTime ID
--------- ----------- ----------- -------------------- ------------
ACTIVE index.js:21 b-1648008775
ACTIVE index.js:21 b-1648044994
ACTIVE index.js:21 b-1648045010
COMPLETED index.js:21 2022-03-23T02:52:23Z b-1648003845
```
### Get snapshot
Get a snapshot with the following command:
```
snapshot-dbg-cli get_snapshot b-1649947203 --debuggee-id d-8dd7f149
```
Where:
* `b-1649947203` is the snapshot ID
* `d-8dd7f149` is the debuggee ID
The output resembles the following:
```
--------------------------------------------------------------------------------
| Summary
--------------------------------------------------------------------------------
Location: index.js:30
Condition: No condition set.
Expressions: No expressions set.
Status: Complete
Create Time: 2022-05-13T14:14:01Z
Final Time: 2022-05-13T14:14:02Z
-------------------------------------------------------------------------------
| Evaluated Expressions
--------------------------------------------------------------------------------
There were no expressions specified.
--------------------------------------------------------------------------------
| Local Variables For Stack Frame Index 0:
--------------------------------------------------------------------------------
[
{
"req (IncomingMessage) ": {
"_readableState (ReadableState) ": {
"objectMode": "false",
"highWaterMark": "16384",
"buffer (BufferList) ": {
"head": null,
"tail": null,
"length": "0"
},
[... snip]
--------------------------------------------------------------------------------
| CallStack:
--------------------------------------------------------------------------------
Function Location
-------------------- -----------
(anonymous function) index.js:30
```
### Set Logpoints
Adds a debug logpoint to a debug target (debuggee). Logpoints inject logging
into running services without changing your code or restarting your application.
Every time any instance executes code at the logpoint location, Snapshot
Debugger logs a message. Output is sent to the standard log for the programming
language of the target (java.logging for Java, logging for Python, etc.)
Logpoints remain active for 24 hours after creation, or until they are deleted
or the service is redeployed. If you place a logpoint on a line that receives
lots of traffic, Debugger throttles the logpoint to reduce its impact on your
application.
Set logpoints with the following command:
```
snapshot-dbg-cli set_logpoint index.js:21 "a={a} b={b}" --debuggee-id d-8dd7f149
```
Where:
* `index.js:21` is the `file:line` for the logpoint
* `a={a} b={b}` is the logpoint message format
* `d-8dd7f149` is the debuggee ID
> **Note**: A common issue that users have run into is that logging at INFO
level is often suppressed by the default logger and so logpoints will appear to
be broken. See the `--log-level` option for setting a higher priority log level.
#### Logpoint message format
The format string is the message which will be logged every time the logpoint
location is executed. If the string contains curly braces ('{' and '}'), any
text within the curly braces will be interpreted as a run-time expression in the
debug target's language, which will be evaluated when the logpoint is hit. Some
valid examples are {a}, {myObj.myFunc()} or {a + b}. The value of the
expression will then replace the {} expression in the resulting log output. For
example, if you specify the format string "a={a}, (b+1)={b+1}", and the logpoint
is hit when local variable a is 1 and b is 3, the resulting log output would be
"a=1, (b+1)=3".
For more detailed information on valid expressions see [Snapshot
expressions](#snapshot-expressions-optional) as the rules are the same for
logpoint expressions.
#### Logpoint conditions (optional)
A logpoint condition is a simple expression in the application language that
must evaluate to true for the logpoint to be logged. Logpoint conditions are
evaluated each time the line is executed, by any instance, until the logpoint
expires or is deleted.
Use of logpoint conditions is optional.
For more detailed information on valid conditions see [Snapshot
conditions](#snapshot-conditions-optional) as the rules are the same for
logpoint conditions.
### List logpoints
List logpoints with the following command:
```
snapshot-dbg-cli list_logpoints --debuggee-id d-8dd7f149 --include-inactive
```
Where:
* `d-8dd7f149` is the debuggee ID
The output resembles the following:
```
User Email Location Condition Log Level Log Message Format ID Status
------------ -------------- --------- --------- ------------------- ------------ -------------------------------------------
foo1@bar.com Main.java:23 INFO a={a} b={b} b-1660681047 EXPIRED
foo2@bar.com Main.java:25 a == 3 WARNING Line hit b-1660932877 EXPIRED
foo2@bar.com Main.java:9999 INFO Log msg b-1661203071 SOURCE_LOCATION: No code found at line 9999
```
### Get logpoint
Get a logpoint with the following command:
```
snapshot-dbg-cli get_logpoint b-1660681047 --debuggee-id d-8dd7f149
```
Where:
* `b-1660681047` is the logpoint ID
* `d-8dd7f149` is the debuggee ID
The output resembles the following:
```
Logpoint ID: b-1660681047
Log Message Format: a == 3
Location: Main.java:23
Condition: No condition set
Status: EXPIRED
Create Time: 2022-08-19T18:14:38Z
Final Time: 2022-08-20T18:14:39Z
User Email: foo1@bar.com
```
## Cleaning up
The following commands can be used to delete debuggees and breakpoints
(snapshots and logpoints).
### Delete Debuggees
Run the following command
```
snapshot-dbg-cli delete_debuggees
```
The output resembles the following:
```
This command will delete the following debuggees:
Name ID Last Active Status
------------------------- ---------- -------------------- ------
default - 20221125t224954 d-39f7082e 2022-12-05T03:13:42Z STALE
default - 20221125t154414 d-dba89292 2022-12-04T03:02:48Z STALE
Do you want to continue (Y/n)?
Deleted 2 debuggees.
```
When deleting a debuggee, all breakpoints that belong to it are also deleted.
### Delete snapshots
Delete snapshots with the following command:
```
snapshot-dbg-cli delete_snapshots --debuggee-id d-8dd7f149 --include-inactive
```
Where:
* `d-8dd7f149` is the debuggee ID
The output resembles the following:
```
This command will delete the following snapshots:
Status Location Condition ID
--------- ----------- ----------- ------------
ACTIVE index.js:28 b-1649959801
ACTIVE index.js:27 b-1649959807
COMPLETED index.js:19 b-1649702213
COMPLETED index.js:22 b-1649702753
Do you want to continue (Y/n)? Y
Deleted 4 snapshots.
```
### Delete logpoints
Delete logpoints with the following command:
```
snapshot-dbg-cli delete_snapshots --debuggee-id d-8dd7f149 --include-inactive
```
Where:
* `d-8dd7f149` is the debuggee ID
The output resembles the following:
```
This command will delete the following logpoints:
Location Condition Log Level Log Message Format ID
--------------- --------- --------- ------------------ ------------
Main.java:25 a == 3 WARNING Line hit b-1660927187
Main.java:9999 INFO Log msg b-1660927272
Do you want to continue (Y/n)?
Deleted 4 snapshots.
```
## VSCode Extension
There is a VSCode extension for the Snapshot Debugger. You can use this
extension to set logpoints, set breakpoints and view snapshots in the comfort
of your IDE. See the [extension's README][extension-readme] for more details.
You can install the extension by downloading it from the
[most recent release][extension-release], and then running
`code --install-extension snapshotdbg-*.vsix`.
Note that you will still need to use the Snapshot Debugger CLI to set up your
environment and to purge old data. Gcloud needs to be installed for credential
management.
[extension-release]: https://github.com/GoogleCloudPlatform/snapshot-debugger/releases
[extension-readme]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/snapshot_dbg_extension/README.md
## Troubleshooting
See [Snapshot Debugger Troubleshooting][troubleshooting]
[troubleshooting]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/troubleshooting.md
## Firebase DB Schema
See [Snapshot Debugger Firebase DB Schema][schema]
[schema]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/SCHEMA.md
Raw data
{
"_id": null,
"home_page": "https://github.com/GoogleCloudPlatform/snapshot-debugger",
"name": "snapshot-dbg-cli",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "cloud,snapshot,debugger",
"author": "Google Inc.",
"author_email": "",
"download_url": "https://files.pythonhosted.org/packages/d9/53/febdfd6f5ddefede39788d114b04d26f492b3b6dbccffe5c3f83544b656b/snapshot-dbg-cli-0.3.8.tar.gz",
"platform": null,
"description": "# Snapshot Debugger\n\nThe Snapshot Debugger lets you inspect the state of a running cloud\napplication, at any code location, without stopping or slowing it down. It\u2019s not\nyour traditional process debugger but rather an always on, whole app debugger\ntaking snapshots from any instance of the app.\n\nYou can use the Snapshot Debugger with any deployment of your application,\nincluding test, development, and production. The debugger typically adds less\nthan 10ms to the request latency only when the application state is captured. In\nmost cases, this isn\u2019t noticeable by users.\n\n\n## Project Status: Archived\n\nThis project has been archived and is no longer supported. There will be no\nfurther bug fixes or security patches. The repository can be forked by users\nif they want to maintain it going forward. \n\nThis OSS solution provides an alternative to Cloud Debugger. Cloud Debugger was\ndeprecated on May 16, 2022 and the service was shut down on May 31, 2023\n\n\n## Limitations\n\n* Python 2.7 is not supported\n\n\n## CLI Command Reference\n\nSee\n[COMMAND_REFERENCE.md](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/snapshot_dbg_cli/COMMAND_REFERENCE.md).\n\n## Installing the Snapshot Debugger CLI\n\nInstall the debugger CLI in your local environment, or in your Cloud Shell\n$HOME directory. See [Using Cloud\nShell](https://cloud.google.com/shell/docs/using-cloud-shell) for information on\nusing Cloud Shell.\n\n```\npython3 -m pip install snapshot-dbg-cli\n```\n\n> **Note**: When using the Snapshot Debugger in Cloud Shell you will be asked to\nAuthorize using your account credentials.\n\n\n## Running the Snapshot Debugger CLI\n\nThere are two options to run the CLI once the pip install has been completed.\n\n### Option 1: Use the installed script\n\nAs part of the pip install process, a script, `snapshot-dbg-cli` will be\ninstalled which can be used to run the CLI.\n\nExample running the `list_debuggees` command:\n\n```\nsnapshot-dbg-cli list_debuggees\n```\n\n> **NOTE**: To run the script this way from any directory, you must ensure the\nscript's install directory is in your PATH. Pip should emit a warning if the\ninstall location is not in the PATH, and also provide the install location in\nthis case, so that you can add it to your PATH.\n\n### Option 2: Run the package directly\n\nExample running the `list_debuggees` command:\n\n```\npython3 -m snapshot_dbg_cli list_debuggees\n```\n\n\n## Before you begin\n\n### Ensure you have the proper permissions\n\nTo complete the setup you\u2019ll need to have the following permissions in your\nGoogle Cloud project. If you are an `Owner` or `Editor` of the Google Cloud\nproject, then you have these permissions.\n\n* firebase.projects.create\n* firebase.projects.update,\n* firebasedatabase.instances.create\n* firebasedatabase.instances.get\n* resourcemanager.projects.get\n* serviceusage.services.enable\n* serviceusage.services.get\n\nFor more information on permissions and roles in Google projects, read\n[Understanding\nroles](https://cloud.google.com/iam/docs/understanding-roles#firebase-roles)\n\n\n### Using Snapshot Debugger in Cloud Shell\n\nSnapshot Debugger requires Python 3.6 or above and the `gcloud` CLI. If you are\nworking in Cloud Shell, you already have Python and `gcloud` installed.\n\nIn addition, the environment should already configured correctly by default. You\ncan verify this by running the following commands:\n\n1. `gcloud config get-value project`\n2. `gcloud config get-value account`\n\n> **NOTE**: When running the cli, you may encounter a popup warning you that\n`gcloud is requesting your credentials to make a GCP API call`. You'll need to\nclick `AUTHORIZE` to proceed.\n\n\n### Using Snapshot Debugger outside of Cloud Shell\n\n#### Ensure you have Python 3.6 or above installed\n\nThe Snapshot Debugger CLI requires [Python](https://www.python.org/downloads/)\n3.6 or newer.\n\n#### Install Google Cloud `gcloud` CLI\n\nThe Snapshot Debugger CLI depends on the `gcloud` CLI. To install the `gcloud`\nCLI, follow these [instructions](https://cloud.google.com/sdk/docs/install). If\nyou already have the `gcloud` CLI installed, run `gcloud components update` to\nupdate all of your installed components to the latest version.\n\n#### Set up the environment\n\n1. Run `gcloud auth login`, be sure to use the account that has permissions on\n the Google Cloud project you are working on.\n2. Run `gcloud config set project PROJECT_ID`. Where PROJECT_ID is the project\n you want to use. The Snapshot Debugger CLI always acts on the current\n `gcloud` configured project.\n\n## Enable Firebase for your Google Cloud Project\n\nThe Snapshot Debugger CLI and agents use a Firebase Realtime Database (RTDB) to\ncommunicate.\n\nIf you already use Firebase in your project, skip to the [Set up the Firebase\nRTDB](#set-up-the-firebase-rtdb) section.\n\n1. Add Firebase to your project:\n\n https://console.firebase.google.com/?dlAction=MigrateCloudProject&cloudProjectNumber=PROJECT_ID\n\n Where PROJECT_ID is your project ID\n\n2. Select your\n [Project ID](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects)\n and click **Continue**. If you have billing enabled in your project, the\n pay-as-you-go Blaze plan is selected, otherwise the free Spark plan is\n selected. If you have billing enabled and want to use the free Spark plan,\n set up a new project without billing enabled.\n\n Note: The Snapshot Debugger uses the Firebase RTDB service. Most users' usage\n will be low enough to remain under the [free usage\n limits](https://firebase.google.com/pricing?).\n\n3. If you are using the pay-as-you-go Blaze plan, click **Confirm plan**. You\n are not prompted to confirm if you are on the free Spark plan.\n\n4. Read the information under **A Few things to remember when adding Firebase to\n a Google Cloud project** then click **Continue**.\n\n5. Toggle the **enable analytics** option to enable or disable Google Analytics\n for Firebase. Google Analytics isn't required for Debugger use.\n\n6. Click **Continue**.\n\n7. Click **Get Started**.\n\n8. Click on your project.\n\n### Set up the Firebase RTDB\n\nThe instructions are slightly different depending on whether you are on the\nSpark or Blaze billing plan. Follow the steps in the following section for the\nplan you have.\n\nYou can check what billing plan is in effect for your project on the Firebase Usage & Billing page:\n\nhttps://console.firebase.google.com/project/PROJECT_ID/usage/details\n\nWhere PROJECT_ID is your project ID\n\n#### Blaze plan RTDB setup\n\nThis will instruct the debugger CLI to create and use a database with the name\n`PROJECT_ID-cdbg`\n\n1. Run `snapshot-dbg-cli init`.\n2. The output resembles the following:\n\n```\nProject 'test-proj' is successfully configured with the Firebase Realtime\nDatabase for use by Snapshot Debugger.\n\nThe full database information is below. If you have specified a custom database\nID the url below is the one you'll need to specify when using the other cli\ncommands.\n\n name: projects/23498723497/locations/us-central1/instances/test-proj-cdbg\n project: projects/23498723497\n database url: https://test-proj-cdbg.firebaseio.com\n type: USER_DATABASE\n state: ACTIVE\n```\n\nNote: The information printed by the `init` command can be accessed from within\nyour Firebase project. It\u2019s safe to run the `snapshot-dbg-cli init` command\nmultiple times to view this information.\n\n#### Spark plan RTDB setup\n\nThis will instruct the CLI to create and use a database with the name\n`PROJECT_ID-default-rtdb`. It will only be created if it does not currently\nexist.\n\n1. Run `snapshot-dbg-cli init --use-default-rtdb`\n2. The output resembles the following:\n\n```\nProject 'test-proj' is successfully configured with the Firebase Realtime\nDatabase for use by Snapshot Debugger.\n\nThe full database information is below. If you have specified a custom database\nID the url below is the one you'll need to specify when using the other cli\ncommands.\n\n name: projects/23498723497/locations/us-central1/instances/default\n project: projects/23498723497\n database url: https://test-proj-default-rtdb.firebaseio.com\n type: USER_DATABASE\n state: ACTIVE\n```\n\nNote: The information printed by the `init` command can be accessed from within\nyour Firebase project. It\u2019s safe to run the `snapshot-dbg-cli init\n--use-default-rtdb` command multiple times to view this information.\n\n#### Setting up Firebase RTDB in other regions\n\nBy default, `snapshot-dbg-cli init` will create a Firebase Realtime Database in\n`us-central1`. It is possible to create and use a database in any region\nsupported by Firebase Realtime Database. See\n[supported RTDB locations][rtdb_locations].\n\nSetting up your database in a non-default region comes with some trade-offs:\n* As a positive, you get to control where your snapshot data will be stored.\n This may be important for compliance reasons.\n* As a negative, the vsCode extension and agents will be unable to\n automatically find the database. The database URL will need to be provided\n explicitly via configuration, see the following for details:\n * [Configuring the Java Agent][java_agent_config]\n * [Configuring the Python Agent][python_agent_config]\n * [Configuring the Node.js Agent][nodejs_agent_config]\n * [Configuring the VsCode Extension][extension_config]\n\nYou can set up your database in a non-default location as follows:\n```\nsnapshot-dbg-cli init --location={YOUR_LOCATION}\n```\n\nFor example, you may want to set up your database in Belgium, and so would run\n```snapshot-dbg-cli init --location=europe-west1```\n\nMake note of the database URL provided in the command output; you will need to\nprovide this to your debug agent(s) and the vsCode plugin.\n\n[rtdb_locations]: https://firebase.google.com/docs/projects/locations#rtdb-locations\n[java_agent_config]: https://github.com/GoogleCloudPlatform/cloud-debug-java/blob/main/README.md#configuring-the-firebase-realtime-database-url\n[python_agent_config]: https://github.com/GoogleCloudPlatform/cloud-debug-python/blob/main/README.md#flag-reference\n[nodejs_agent_config]: https://github.com/googleapis/cloud-debug-nodejs/blob/main/README.md#debugger-agent-settings\n[extension_config]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/snapshot_dbg_extension/README.md#configuration\n\n\n## Set up Snapshot Debugger in your Google Cloud project\n\n### Working Samples\n\nWorking examples of using the Snapshot Debugger with Java, Python and Node.js\napplications across different Google Cloud environments can be found in:\n\n* [snapshot-debugger/samples][samples]\n\n[samples]: https://github.com/GoogleCloudPlatform/snapshot-debugger/tree/main/samples\n[notes-local]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/samples/README.md#notes-on-running-locally\n\n### Agent Documentation\n\nSee the following for agent specific documentation:\n\n* [Java](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/java.md)\n* [Node.js](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/node-js.md)\n* [Python](https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/python.md)\n\n## Example workflow\n\nYou create a breakpoint (snapshot or logpoint) on debuggees. Debuggees represent\ninstances of the running application. In general all instances of the same\nversion of the application will have the same debuggee ID, and breakpoints set\non a debuggee will be installed on all running instances of it.\n\n### List Debuggees\n\nRun the following command\n\n```\nsnapshot-dbg-cli list_debuggees --include-inactive\n```\n\nThe output resembles the following:\n\n```\nName ID Description Last Active Status\n------------- ---------- ---------------------------------------- -------------------- --------\ntest-app - v2 d-8dd7f149 node index.js module:test-app version:v2 2022-12-16T21:45:07Z ACTIVE\ntest-app - v1 d-24abc4f1 node index.js module:test-app version:v1 2022-10-16T21:45:07Z INACTIVE\n```\n\n\n### Set Snapshots\n\nSnapshots capture local variables and the call stack at a specific line location\nin your app's source code. You can specify certain conditions and locations to\nreturn a snapshot of your app's data, and view it in detail to debug your app.\n\nSet snapshots with the following command:\n\n```\nsnapshot-dbg-cli set_snapshot index.js:21 --debuggee-id d-8dd7f149\n```\n\nWhere:\n* `index.js:21` is the `file:line` for the snapshot\n* `d-8dd7f149` is the debuggee ID\n\n\n#### Snapshot conditions (optional)\n\nA snapshot condition is a simple expression in the app's language that must\nevaluate to true for the snapshot to be taken. Snapshot conditions are evaluated\neach time the line is executed, by any instance, until the condition evaluates\nto true or the snapshot times out.\n\nUse of snapshot conditions is optional.\n\nThe condition is a full boolean expression that can include logical operators.\nConditions are specified using the `--condition` flag of the `set_snapshots`\ncommand.\n\nExample:\n```\nsnapshot-dbg-cli set_snapshot index.js:26 --debuggee-id d-8dd7f149 --condition=\"ultimateAnswer <= 42 && foo==bar\"\n```\n\nYou can use the following language features to express conditions:\n\n##### Java\n\nMost Java expressions are supported, including:\n\n* Local variables: `a == 8`.\n* Numerical and boolean operations: `x + y < 20`.\n* Instance and static fields: `this.counter == 20`, `this.myObj.isShutdown`,\n `myStatic`, or `com.mycompany.MyClass.staticMember`.\n* String comparisons with the equality operator: `myString == \"abc\"`.\n* Function calls. Only read-only functions can be used. For example,\n `StringBuilder.indexOf()` is supported, but `StringBuilder.append()` is not.\n* Type casting, with fully qualified types: `((com.myprod.ClassImpl)\n myInterface).internalField`\n\nThe following language features are *not* supported:\n\n* Unboxing of numeric types, such as `Integer`; use `myInteger.value` instead.\n\n\n##### Python\n\nMost Python expressions are supported, including:\n\n* Reading local and global variables.\n* Reading from arrays, lists, slices, dictionaries and objects.\n* Calling simple methods.\n\nThe following language features are not supported:\n\n* Calling functions that allocate new objects or use complex constructs.\n* Creating new objects inside the expression.\n\n##### Node.js\n\nMost Javascript expressions are supported, with the following caveat:\n\nExpressions that may have static side effects are disallowed. The debug agent\nensures all conditions and watchpoints you add are read-only and have no side\neffects, however, it doesn\u2019t catch expressions that have dynamic side-effects.\n\nFor example, `o.f` looks like a property access, but dynamically, it may end up\ncalling a getter function. The debugger presently doesn't detect such\ndynamic-side effects.\n\n\n#### Snapshot expressions (optional)\n\nSnapshot Debugger's Expressions feature allows you to evaluate complex\nexpressions or traverse object hierarchies when a snapshot is taken. Expressions\nsupport the same language features as [snapshot conditions](#snapshot-conditions-optional), described above.\n\nUse of expressions is optional.\n\nTypical uses for expressions are:\n\n* To view static or global variables that are not part of the local variable\n set.\n* To easily view deeply nested member variables.\n* To avoid repetitive mathematical calculations. For example, calculating a\n duration in seconds with `(endTimeMillis - startTimeMillis) / 1000.0`.\n\nExpressions are specified using the --expression flag of the set_snapshots\ncommand.\n\nExample:\n```\nsnapshot-dbg-cli set_snapshot index.js:26 --debuggee-id d-8dd7f149 --expression=\"histogram.length\"\n```\n\n\n### List snapshots\n\nList snapshots with the following command:\n\n```\nsnapshot-dbg-cli list_snapshots --debuggee-id d-8dd7f149 --include-inactive\n```\n\nWhere:\n* `d-8dd7f149` is the debuggee ID\n\nThe output resembles the following:\n\n```\nStatus Location Condition CompletedTime ID\n--------- ----------- ----------- -------------------- ------------\nACTIVE index.js:21 b-1648008775\nACTIVE index.js:21 b-1648044994\nACTIVE index.js:21 b-1648045010\nCOMPLETED index.js:21 2022-03-23T02:52:23Z b-1648003845\n```\n\n### Get snapshot\n\nGet a snapshot with the following command:\n\n```\nsnapshot-dbg-cli get_snapshot b-1649947203 --debuggee-id d-8dd7f149\n```\n\nWhere:\n* `b-1649947203` is the snapshot ID\n* `d-8dd7f149` is the debuggee ID\n\nThe output resembles the following:\n\n```\n--------------------------------------------------------------------------------\n| Summary\n--------------------------------------------------------------------------------\n\nLocation: index.js:30\nCondition: No condition set.\nExpressions: No expressions set.\nStatus: Complete\nCreate Time: 2022-05-13T14:14:01Z\nFinal Time: 2022-05-13T14:14:02Z\n\n-------------------------------------------------------------------------------\n| Evaluated Expressions\n--------------------------------------------------------------------------------\n\nThere were no expressions specified.\n\n--------------------------------------------------------------------------------\n| Local Variables For Stack Frame Index 0:\n--------------------------------------------------------------------------------\n\n[\n {\n \"req (IncomingMessage) \": {\n \"_readableState (ReadableState) \": {\n \"objectMode\": \"false\",\n \"highWaterMark\": \"16384\",\n \"buffer (BufferList) \": {\n \"head\": null,\n \"tail\": null,\n \"length\": \"0\"\n },\n[... snip]\n\n--------------------------------------------------------------------------------\n| CallStack:\n--------------------------------------------------------------------------------\n\nFunction Location\n-------------------- -----------\n(anonymous function) index.js:30\n```\n\n### Set Logpoints\n\nAdds a debug logpoint to a debug target (debuggee). Logpoints inject logging\ninto running services without changing your code or restarting your application.\nEvery time any instance executes code at the logpoint location, Snapshot\nDebugger logs a message. Output is sent to the standard log for the programming\nlanguage of the target (java.logging for Java, logging for Python, etc.)\n\nLogpoints remain active for 24 hours after creation, or until they are deleted\nor the service is redeployed. If you place a logpoint on a line that receives\nlots of traffic, Debugger throttles the logpoint to reduce its impact on your\napplication.\n\nSet logpoints with the following command:\n\n```\nsnapshot-dbg-cli set_logpoint index.js:21 \"a={a} b={b}\" --debuggee-id d-8dd7f149\n```\n\nWhere:\n* `index.js:21` is the `file:line` for the logpoint\n* `a={a} b={b}` is the logpoint message format\n* `d-8dd7f149` is the debuggee ID\n\n> **Note**: A common issue that users have run into is that logging at INFO\nlevel is often suppressed by the default logger and so logpoints will appear to\nbe broken. See the `--log-level` option for setting a higher priority log level.\n\n#### Logpoint message format\n\nThe format string is the message which will be logged every time the logpoint\nlocation is executed. If the string contains curly braces ('{' and '}'), any\ntext within the curly braces will be interpreted as a run-time expression in the\ndebug target's language, which will be evaluated when the logpoint is hit. Some\nvalid examples are {a}, {myObj.myFunc()} or {a + b}. The value of the\nexpression will then replace the {} expression in the resulting log output. For\nexample, if you specify the format string \"a={a}, (b+1)={b+1}\", and the logpoint\nis hit when local variable a is 1 and b is 3, the resulting log output would be\n\"a=1, (b+1)=3\".\n\nFor more detailed information on valid expressions see [Snapshot\nexpressions](#snapshot-expressions-optional) as the rules are the same for\nlogpoint expressions.\n\n#### Logpoint conditions (optional)\n\nA logpoint condition is a simple expression in the application language that\nmust evaluate to true for the logpoint to be logged. Logpoint conditions are\nevaluated each time the line is executed, by any instance, until the logpoint\nexpires or is deleted.\n\nUse of logpoint conditions is optional.\n\nFor more detailed information on valid conditions see [Snapshot\nconditions](#snapshot-conditions-optional) as the rules are the same for\nlogpoint conditions.\n\n\n### List logpoints\n\nList logpoints with the following command:\n\n```\nsnapshot-dbg-cli list_logpoints --debuggee-id d-8dd7f149 --include-inactive\n```\n\nWhere:\n* `d-8dd7f149` is the debuggee ID\n\nThe output resembles the following:\n\n```\nUser Email Location Condition Log Level Log Message Format ID Status\n------------ -------------- --------- --------- ------------------- ------------ -------------------------------------------\nfoo1@bar.com Main.java:23 INFO a={a} b={b} b-1660681047 EXPIRED\nfoo2@bar.com Main.java:25 a == 3 WARNING Line hit b-1660932877 EXPIRED\nfoo2@bar.com Main.java:9999 INFO Log msg b-1661203071 SOURCE_LOCATION: No code found at line 9999\n```\n\n\n### Get logpoint\n\nGet a logpoint with the following command:\n\n```\nsnapshot-dbg-cli get_logpoint b-1660681047 --debuggee-id d-8dd7f149\n```\n\nWhere:\n* `b-1660681047` is the logpoint ID\n* `d-8dd7f149` is the debuggee ID\n\nThe output resembles the following:\n\n```\nLogpoint ID: b-1660681047\nLog Message Format: a == 3\nLocation: Main.java:23\nCondition: No condition set\nStatus: EXPIRED\nCreate Time: 2022-08-19T18:14:38Z\nFinal Time: 2022-08-20T18:14:39Z\nUser Email: foo1@bar.com\n```\n\n## Cleaning up\n\nThe following commands can be used to delete debuggees and breakpoints\n(snapshots and logpoints).\n\n### Delete Debuggees\n\nRun the following command\n\n```\nsnapshot-dbg-cli delete_debuggees\n```\n\nThe output resembles the following:\n\n```\nThis command will delete the following debuggees:\n\nName ID Last Active Status\n------------------------- ---------- -------------------- ------\ndefault - 20221125t224954 d-39f7082e 2022-12-05T03:13:42Z STALE\ndefault - 20221125t154414 d-dba89292 2022-12-04T03:02:48Z STALE\n\n\n\nDo you want to continue (Y/n)?\nDeleted 2 debuggees.\n```\n\nWhen deleting a debuggee, all breakpoints that belong to it are also deleted.\n\n### Delete snapshots\n\nDelete snapshots with the following command:\n\n```\nsnapshot-dbg-cli delete_snapshots --debuggee-id d-8dd7f149 --include-inactive\n```\n\nWhere:\n* `d-8dd7f149` is the debuggee ID\n\nThe output resembles the following:\n\n```\nThis command will delete the following snapshots:\n\nStatus Location Condition ID\n--------- ----------- ----------- ------------\nACTIVE index.js:28 b-1649959801\nACTIVE index.js:27 b-1649959807\nCOMPLETED index.js:19 b-1649702213\nCOMPLETED index.js:22 b-1649702753\n\n\nDo you want to continue (Y/n)? Y\nDeleted 4 snapshots.\n```\n\n\n### Delete logpoints\n\nDelete logpoints with the following command:\n\n```\nsnapshot-dbg-cli delete_snapshots --debuggee-id d-8dd7f149 --include-inactive\n```\n\nWhere:\n* `d-8dd7f149` is the debuggee ID\n\nThe output resembles the following:\n\n```\nThis command will delete the following logpoints:\n\nLocation Condition Log Level Log Message Format ID\n--------------- --------- --------- ------------------ ------------\nMain.java:25 a == 3 WARNING Line hit b-1660927187\nMain.java:9999 INFO Log msg b-1660927272\n\n\n\nDo you want to continue (Y/n)?\nDeleted 4 snapshots.\n```\n\n\n## VSCode Extension\n\nThere is a VSCode extension for the Snapshot Debugger. You can use this\nextension to set logpoints, set breakpoints and view snapshots in the comfort\nof your IDE. See the [extension's README][extension-readme] for more details.\n\nYou can install the extension by downloading it from the\n[most recent release][extension-release], and then running\n`code --install-extension snapshotdbg-*.vsix`.\n\nNote that you will still need to use the Snapshot Debugger CLI to set up your\nenvironment and to purge old data. Gcloud needs to be installed for credential\nmanagement.\n\n[extension-release]: https://github.com/GoogleCloudPlatform/snapshot-debugger/releases\n[extension-readme]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/snapshot_dbg_extension/README.md\n\n## Troubleshooting\n\nSee [Snapshot Debugger Troubleshooting][troubleshooting]\n\n[troubleshooting]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/troubleshooting.md\n\n## Firebase DB Schema\n\nSee [Snapshot Debugger Firebase DB Schema][schema]\n\n[schema]: https://github.com/GoogleCloudPlatform/snapshot-debugger/blob/main/docs/SCHEMA.md\n",
"bugtrack_url": null,
"license": "Apache License, Version 2.0",
"summary": "'Snapshot Debugger CLI tool.'",
"version": "0.3.8",
"project_urls": {
"CLI Source": "https://github.com/GoogleCloudPlatform/snapshot-debugger",
"Homepage": "https://github.com/GoogleCloudPlatform/snapshot-debugger",
"Java Agent Source": "https://github.com/GoogleCloudPlatform/cloud-debug-java",
"Node.js Agent Source": "https://github.com/googleapis/cloud-debug-nodejs",
"Python Agent Source": "https://github.com/GoogleCloudPlatform/cloud-debug-python"
},
"split_keywords": [
"cloud",
"snapshot",
"debugger"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "ff3c41fdb1ba8d02353769b1a4d891c77b41600eda95f6220fc3647a9a134ec7",
"md5": "7d00f036088eab42e4419572fb180ea7",
"sha256": "c7bde0d11a6c9dd00c9c92ce4dea076fd234c66dd9bb402cafcb48f44e044be0"
},
"downloads": -1,
"filename": "snapshot_dbg_cli-0.3.8-py3-none-any.whl",
"has_sig": false,
"md5_digest": "7d00f036088eab42e4419572fb180ea7",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 86133,
"upload_time": "2023-09-06T19:56:56",
"upload_time_iso_8601": "2023-09-06T19:56:56.480926Z",
"url": "https://files.pythonhosted.org/packages/ff/3c/41fdb1ba8d02353769b1a4d891c77b41600eda95f6220fc3647a9a134ec7/snapshot_dbg_cli-0.3.8-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "d953febdfd6f5ddefede39788d114b04d26f492b3b6dbccffe5c3f83544b656b",
"md5": "488f8802a2b70608ef31aa891a700c9c",
"sha256": "badaa5b8e3837165b123e9b3801890ab09aa76aee00796471fb6f10c41c37446"
},
"downloads": -1,
"filename": "snapshot-dbg-cli-0.3.8.tar.gz",
"has_sig": false,
"md5_digest": "488f8802a2b70608ef31aa891a700c9c",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 64261,
"upload_time": "2023-09-06T19:56:58",
"upload_time_iso_8601": "2023-09-06T19:56:58.119522Z",
"url": "https://files.pythonhosted.org/packages/d9/53/febdfd6f5ddefede39788d114b04d26f492b3b6dbccffe5c3f83544b656b/snapshot-dbg-cli-0.3.8.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-09-06 19:56:58",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "GoogleCloudPlatform",
"github_project": "snapshot-debugger",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "snapshot-dbg-cli"
}
JSON
