ansible-apply: apply remote tasks, supports command line inventory
Ansible-apply takes the tasks file spec as first argument:
ansible-apply role.name ansible-apply role.name/some_tasks ansible-apply https://some/playbook.yml ansible-apply ./playbook.yml
It will automatically download the playbook or role if not found.
Then, the command takes any number of hosts and inventory variables on the command line:
ansible-apply role.name server1 server2 update=true
Finnaly, any argument passed with dashes are forwarded to the ansible-playbook command it generates, but named args must use the = notation, and not a space to not confuse the command line parser:
# works: ansible-apply role.name server2 update=true --become-user=root # does not: ansible-apply role.name server2 update=true --become-user root
Release files for bigsudo 0.1.2.post11
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 |
|---|---|---|---|---|
| bigsudo-0.1.2.post11.tar.gz | 1.6 kB | Without provenance | Details for bigsudo-0.1.2.post11.tar.gz |
Release files / bigsudo-0.1.2.post11.tar.gz
| Download URL | bigsudo-0.1.2.post11.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d6488e4f517832b29f5dba1004f894d21a73ddc09943a11069fd5a83282c4d7
|
|
BLAKE2b-256 checksum How to use checksums |
dd691341746748c054b7e3a05466e04478e8dee2bdcef313919dfbbf68aee115
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.8
|
Security for bigsudo 0.1.2.post11
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.
