diff options
| author | saranti <tsarantis@proton.me> | 2022-11-18 04:00:25 +1100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-17 12:00:25 -0500 |
| commit | b7ea661807449919c36fe60b22a9406258808f7a (patch) | |
| tree | 6db2a031adc118f6263948c7b4fccc375850be82 | |
| parent | 6059116a64afd4d53d82f846f9c3342ab21f9b7c (diff) | |
| download | ansible-b7ea661807449919c36fe60b22a9406258808f7a.tar.gz | |
Update pull.py (#79387)
| -rwxr-xr-x | lib/ansible/cli/pull.py | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/lib/ansible/cli/pull.py b/lib/ansible/cli/pull.py index 99da8c4f0f..dc8f055b44 100755 --- a/lib/ansible/cli/pull.py +++ b/lib/ansible/cli/pull.py @@ -38,6 +38,9 @@ class PullCLI(CLI): This inverts the default *push* architecture of ansible into a *pull* architecture, which has near-limitless scaling potential. + None of the CLI tools are designed to run concurrently with themselves, + you should use an external scheduler and/or locking to ensure there are no clashing operations. + The setup playbook can be tuned to change the cron frequency, logging locations, and parameters to ansible-pull. This is useful both for extreme scale-out as well as periodic remediation. Usage of the 'fetch' module to retrieve logs from ansible-pull runs would be an |