Gridworks Debug Cli
Internal debugging tools for Gridworks systems:
brew install awscli
aws configure
pip install gridworks-debug-cli
gwd --help
gwd csv --help
gwd csv egd --help
gwd events --help
gwd events mkconfig
gwd events show
This tool will be maintained only as long as it is internally useful. YMMV.
Features
- Event viewing, either from local directory of events or from the cloud, via
eventssubcommand. - Data download, via
csvsubcommand.
Requirements
- awscli. This should be installable
per Amazon instructions or on a
mac with:
brew install awscli
- AWS credentials from Gridworks installed per
Amazon instructions or:
aws configure
Installation
You can install Gridworks Debug Cli via pip from PyPI:
Install awscli per per Amazon instructions or on a mac with:
brew install awscli
Get AWS credentials from Gridworks and install them with:
aws configure
Install gridworks-debug-cli with:
pip install gridworks-debug-cli
Vieweing events
Configure events subcommand with:
gwd events mkconfig
open $HOME/.config/gridworks/debug-cli/events/gwd.events.config.json
You must fill in values for the following keys with information from Gridworks:
{
"mqtt": {
"hostname": "USE REAL VALUE",
"password": "USE REAL VALUE",
"username": "USE REAL VALUE"
},
"sync": {
"s3": {
"bucket": "USE REAL VALUE",
"prefix": "USE REAL VALUE",
"profile": "USE NAME YOU CHOSE in 'aws configure'"
}
}
}
Data download
Configure csv subcommand with:
gwd csv mkconfig
open $HOME/.config/gridworks/debug-cli/csv/gwd.csv.config.json
Usage
Please see the Command-line Reference for details.
Contributing
Contributions are very welcome. To learn more, see the Contributor Guide.
License
Distributed under the terms of the MIT license, Gridworks Debug Cli is free and open source software.
Issues
If you encounter any problems, please file an issue along with a detailed description.
Credits
This project was generated from @cjolowicz's Hypermodern Python Cookiecutter template.
Metadata
Release files for gridworks-debug-cli 0.3.2
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 |
|---|---|---|---|---|
| gridworks_debug_cli-0.3.2.tar.gz | 23.9 kB | Without provenance | Details for gridworks_debug_cli-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gridworks_debug_cli-0.3.2-py3-none-any.whl | Python 3 | none | any | Details for gridworks_debug_cli-0.3.2-py3-none-any.whl |
Total release size: 52.7 kB
Release files / gridworks_debug_cli-0.3.2.tar.gz
| Download URL | gridworks_debug_cli-0.3.2.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ebde2b37a6c89298cd83e179560a5f6c7a8e2ede2933b19cf1c332ba5aa3fcd
|
|
BLAKE2b-256 checksum How to use checksums |
95b4acc431b9538608d7c5bb698e842c493a06b45991127b2dbc2ff1d8b8a6fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / gridworks_debug_cli-0.3.2-py3-none-any.whl
| Download URL | gridworks_debug_cli-0.3.2-py3-none-any.whl |
|---|---|
| Size | 28.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d0a1259ca8622ab6360e99b1b91d350a1270ed7d8dc278ffdef7a20a03ebf66
|
|
BLAKE2b-256 checksum How to use checksums |
cf8358cf9798de9fefd96f0da50d15d064825c73ae7c8f9b47abf99af6eccfc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for gridworks-debug-cli 0.3.2
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.