Batch Debugging CLI
The Batch Debugging CLI is designed to streamline the debugging process for AWS Batch, GCP, Azure, and Kubernetes compute environments. Leveraging the capabilities of [batch-debugging](https://github.com/Shahbaz-mahmood123/batch-debugging).
Explore the documentation »
Table of Contents
About The Project
The Batch Debugging CLI is a command-line tool designed to assist in debugging batch compute environments across AWS, GCP, Azure, and Kubernetes. It currently relies on batch-debugging for its underlying logic, so refer to its documentation for detailed information on the debugging process.
Please note that the CLI assumes AWS Batch compute environments were built using the Seqera platform. However, a more generic debugging tool will be implemented in the future.
Installation
To use this library, just install the package via pip.
pip install batch-debugging-cli
Getting Started
Before using the CLI, ensure you have an account in your compute provider, a valid compute enviornment and credentials to access the account(AWS, GCP, Azure)
Currently, the CLI supports a few commands, and it expects the environment name to match the corresponding AWS environment. When supplying a compute environment ID, provide the full name of the environment (e.g., TowerForge-1rVcJ5K5wnvky3zohO4EaN-head).
AWS
For AWS please declare the region where your batch enviornmets are located. For example:
export AWS_REGION=us-east-1
Additionally the below IAM permissions are required.
GCP
To use the GCP commands please use the set the below enviornment variables:
export GCP_PROJECT_ID=test-environment
export GCP_REGION=us-central1
For Seqera platform, please declare the below two enviornment variables prior to attempting to run any of the seqera cli commands:
export PLATFORM_TOKEN=
export PLATFORM_URL=
Contact
Shahbaz Mahmood - shahbazmahmooood@gmail.com
Metadata
Release files for batch-debugging-cli 0.0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| batch_debugging_cli-0.0.9.tar.gz | 5.6 kB | Without provenance | Details for batch_debugging_cli-0.0.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| batch_debugging_cli-0.0.9-py3-none-any.whl | Python 3 | none | any | Details for batch_debugging_cli-0.0.9-py3-none-any.whl |
Total release size: 13.1 kB
Release files / batch_debugging_cli-0.0.9.tar.gz
| Download URL | batch_debugging_cli-0.0.9.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab0872cf2b899cd38c94ec4560019c07410f5fe7d6a21552b4076fc954a8b066
|
|
BLAKE2b-256 checksum How to use checksums |
66dbde336fbdd886536a0f321394fef55f5d9d82e57949f820fa92107e9cbe96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.11.7 Darwin/23.3.0
|
Release files / batch_debugging_cli-0.0.9-py3-none-any.whl
| Download URL | batch_debugging_cli-0.0.9-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a320cc976dcecb1d2751f6d39bf856621b7276432ced4a9a94b8c55f3e3e2e03
|
|
BLAKE2b-256 checksum How to use checksums |
0c2a14a1d4f8019ef1e028666163e776882bbb87fd73dfdcf54b12cae5af72d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.11.7 Darwin/23.3.0
|
Security for batch-debugging-cli 0.0.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.