OpsWork
To use opswork, follow the following steps:
Create a python virtual environment or use system wide environment
$ python3 -m venv venv
$ source venv/bin/activateInstall opswork package with pip.
$ pip install opsworkGet opswork command line help
$ opswork --helpInit the config file and the sqlite database
$ opswork config initTo edit configs
$ opswork config initAdd a recipe
$ opswork recipe add <recipe_name> -p <recipe_relative_path>
# Some examples
$ opswork recipe add clivern/ping -p recipe/ping -f
$ opswork recipe add clivern/nginx -p recipe/nginx -f
$ opswork recipe add clivern/motd -p recipe/motd -f
$ opswork recipe add clivern/cmd -p recipe/cmd -f
# From remote git
$ opswork recipe add clivern/dotfiles/update -p git@github.com:clivern/dotfiles.git -s brew/update -t dotfiles -fTo list recipes
$ opswork recipe list
# Get recipes as a JSON
$ opswork recipe list -o json | jq .To get a recipe
$ opswork recipe get <recipe_name>To delete a recipe
$ opswork recipe delete <recipe_name>Add a host
$ opswork host add <host_name> -i <host_ip> -p <ssh_port> -u <ssh_username> -s <ssh_key_path>
# Add a remote host
$ opswork host add example.com -i 127.0.0.1 -p 22 -u root -s /Users/root/.ssh/id_rsa.pem
# Add the localhost
$ opswork host add localhost -i localhost -c localTo list hosts
$ opswork host list
# Get hosts as a JSON
$ opswork host list -o json | jq .To get a host
$ opswork host get <host_name>To SSH into a host
$ opswork host ssh <host_name>To delete a host
$ opswork host delete <host_name>Run a recipe towards a host
$ opswork recipe run <recipe_name> -h <host_name> -v key=value
# Some examples
$ opswork recipe run clivern/nginx -h example.com
$ opswork recipe run clivern/ping -h localhostTo generate a random password
$ opswork random password 8To add a secret
$ opswork secret add <secret/name> <secret_value> -t <tag>
$ opswork secret add clivern/cloud_provider/api_key xxxx-xxxx-xxxx-xxxx -t cloud_providerTo list secrets
$ opswork secret list -o jsonTo get a secret
$ opswork secret get <secret_name>
# For example
$ opswork secret get clivern/cloud_provider/api_keyTo delete a secret
$ opswork secret delete <secret_name>
# For example
$ opswork secret delete clivern/cloud_provider/api_keyTo run a recipe with secrets
# add recipe
$ opswork recipe add clivern/secrets -p recipe/secrets -f
# add secret
$ opswork secret add db_password s3cr3t --force
# run recipe
$ opswork recipe run clivern/secrets -h localhostTo batch load recipes and run them
$ opswork batch load batch.yml --force
$ opswork batch run batch.yml --host localhost1 maintainer
Metadata
1 maintainer
Release files for opswork 0.10.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 | |
|---|---|---|---|---|
| opswork-0.10.2.tar.gz | 23.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opswork-0.10.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.2 kB
Release files / opswork-0.10.2.tar.gz
| Download URL | opswork-0.10.2.tar.gz |
|---|---|
| Size | 23.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10b335396e09100f8cfeff2675f6d500edae6a2bff5c757e4be677c533210f5f
|
|
BLAKE2b-256 checksum How to use checksums |
42f0b3c2186146be1e223afa52d63fdd4403b78cc58416b03df78711f28fcd16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / opswork-0.10.2-py3-none-any.whl
| Download URL | opswork-0.10.2-py3-none-any.whl |
|---|---|
| Size | 34.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
884485c7169a7d719bbbd374f6cf39def30ed9cc528a7ccf67732ddaf10f8b3f
|
|
BLAKE2b-256 checksum How to use checksums |
0f9606007e1de874bb4885642f74ede886b3efba6d14b133871a899f8dcb01a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for opswork 0.10.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.
