Agent
Spotinst Agent executor provides a mechanism to run remote shutdown scripts on machine using polling architecture.
Note: The agent must have token to communicate with spotinst API. The credentials ini that holds the token file must be located at: ‘/root/.spotinst/credentials’
Application
Manual Executing
The simplest way to run the agent is by ‘./agent’ that start and write basic logs to /var/log/messages/agent.log
Otherwise, you can use the following options:
Usage: ./agent [options]
-c –config Use alternate configuration yml file. -l –log Use alternate Log file for output. -t –test Test run. Do not run remote script. -v –verbose verbose log –stdout redirect output to stdout –debug run with dummy credentials for debug purposes
Configuration
There are two levels of configuration representing in yml files. The global configuration ‘agent.yml’ is responsible of the agent framework and necessary params. The worker configuration, located at the workers folder is responsible of the specific workers parameters.
MAKEFILE
run ‘make release’ output file is located in the /dist folder
Documentation
1 maintainer
Metadata
1 maintainer
Release files for spotinst-agent-2-beta 3.1.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 | |
|---|---|---|---|---|
| spotinst-agent-2-beta-3.1.15.tar.gz | 21.2 kB | Without provenance | Details |
Release files / spotinst-agent-2-beta-3.1.15.tar.gz
| Download URL | spotinst-agent-2-beta-3.1.15.tar.gz |
|---|---|
| Size | 21.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1d5db517195ece50050c9d807d5c9c2a2979409720c902c9d5a9e9072e70d31
|
|
BLAKE2b-256 checksum How to use checksums |
19210790b39279f4bd353a634c5ec2ae8037ce28669f53625196ce0736464f6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.3
|
Security for spotinst-agent-2-beta 3.1.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.
