==================
Calls otpl-service-check for each compatible deployment found in a sous
global deploy manifest (GDM).
Writes the results of these checks to the local Sensu client.
Usage
-----
This script is long running, and performs periodic checks,
delivering the results directly to Sensu on ``localhost:3030``.
Dependencies
------------
See ``requirements.txt``.
Notably, see https://github.com/opentable/otpl-service-check
which this script wraps.
Arguments
---------
Run with ``-h`` or ``--help`` to see command-line argument
documentation.
Releasing
---------
Set up PyPI RC file, .pypirc. E.g.:
[distutils]
index-servers =
pypi
pypitest
[pypitest]
repository = https://testpypi.python.org/pypi
username = cpennello_opentable
[pypi]
repository = https://pypi.python.org/pypi
username = cpennello_opentable
Suppose the version being released is a.b.c.
Create distributions:
``python setup.py sdist bdist_wheel``
Sign distribution files:
for x in dist/*a.b.c*;do
gpg --detach-sign -a $x
done
Use Twine, uploading to the test repo first.
``twine upload -r pypitest dist/*a.b.c*``
Then to the real repo.
``twine upload -r pypi dist/*a.b.c*``
2 maintainers
Metadata
2 maintainers
Release files for sous-sensu-checks 0.0.15
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 | |
|---|---|---|---|---|
| sous-sensu-checks-0.0.15.tar.gz | 9.6 kB | Without provenance | Details |
Release files / sous-sensu-checks-0.0.15.tar.gz
| Download URL | sous-sensu-checks-0.0.15.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37a5d8316f39f9c5b75784b52ddc0506fc9176f90ea6afbe42fa178ace25ab85
|
|
BLAKE2b-256 checksum How to use checksums |
865fc01f77bb63e7052a401ae09867987502ccbfc425d4d5137c71312a895690
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sous-sensu-checks 0.0.15
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.
