Python module for interacting with the Zenoss API an an object-oriented way. The philosophy here is to use objects to work with everything in the Zenoss API, and to try to normalize the various calls to the different routers. Thus get methods will always return an object, list methods will return data. All methods to add or create start with add, all remove or delete start with delete. As much as possible the methods try to hide the idiosyncrasies of the JSON API, and to do the work for you, for example by letting you use a device name instead of having to provide the full device UID for every call.
Metadata
Release files for ZenossAPIClient 0.2.7
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 | |
|---|---|---|---|---|
| ZenossAPIClient-0.2.7.tar.gz | 27.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ZenossAPIClient-0.2.7-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 60.3 kB
Release files / ZenossAPIClient-0.2.7.tar.gz
| Download URL | ZenossAPIClient-0.2.7.tar.gz |
|---|---|
| Size | 27.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c59c14bc1ce93ec7185394bca31f0b96f2f01000878eb8e5cd887052edb5d67
|
|
BLAKE2b-256 checksum How to use checksums |
605370218586450de1c2e979e32baed1f1dec0f8cef3d34551eb754334cce125
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/2.7.17
|
Release files / ZenossAPIClient-0.2.7-py2-none-any.whl
| Download URL | ZenossAPIClient-0.2.7-py2-none-any.whl |
|---|---|
| Size | 32.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
c5b6d4e1694fbba8ccc5f81ae631e9dddbef7cc0b167f8502cdb68729212f138
|
|
BLAKE2b-256 checksum How to use checksums |
5d8cc0552fda86d9341bc23083599d3639c5681b5b10ed633482f1a3e3c7063d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/2.7.17
|
Security for ZenossAPIClient 0.2.7
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.