Nessy CLI
Simple command line interface to the Nessy locking system.
Installation
It is simplest to install via PyPI using:
pip install nessy-cli
Usage
For convenience, you should set the nessy server claims URL in your environment:
export NESSY_CLAIMS_URL=http://nessy.example.com/v1/claims
If NESSY_CLAIMS_URL or GENOME_NESSY_SERVER are set in your environment, then those will be used; otherwise, you will need to specify the URL on the command line with the –url option.
To list active claims:
nessy list --status active
To revoke claims matching a filter:
nessy revoke --status active --min-active-duration 100000
To avoid a race condition while trying to revoke a specific claim on a resource, you should add a filter on the active duration:
nessy revoke --status active --min-active-duration 100000 --resource <RESOURCE>
2 maintainers
Metadata
2 maintainers
Release files for nessy-cli 0.8.1
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 |
|---|---|---|---|---|
| nessy-cli-0.8.1.tar.gz | 16.0 kB | Without provenance | Details for nessy-cli-0.8.1.tar.gz |
Release files / nessy-cli-0.8.1.tar.gz
| Download URL | nessy-cli-0.8.1.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cedcf3a7604525a20cb2e19fc5ad850b2ca43267c9b12a31e29d5b88821f43e7
|
|
BLAKE2b-256 checksum How to use checksums |
1fd40e184aa516425255e94f9350e3606b38adef39e4e3d96d46e0e749980840
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nessy-cli 0.8.1
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.
