-
Notifications
You must be signed in to change notification settings - Fork 674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add experimental rule for run_once #2626
Conversation
d06806b
to
98d6b1e
Compare
98d6b1e
to
3fa4c98
Compare
What - a warning will be printed if strategy Edit: this PR is "sneaking" in a second warning that is not discussed or mentioned anywhere. Nowhere is a warning for Or is this because of limitations in ansible-lint? Only way to look at both play level and task level are 2 separate warnings? |
Co-authored-by: Ajinkya <audgirka@redhat.com>
The logic in the rule is giving a warning, whenever I think, there are very legitimate use-cases for this keyword and it can be done in a predictable way. (we actually do this in our infrastructure). Also there's no hint in the Ansible reference docs, that the use of Please reconsider this PR and check only for the risky combination of |
Currently, the rule makes no sense and causes false positives for us. Reference: ansible/ansible-lint#2626
Currently, the rule makes no sense and causes false positives for us. Reference: ansible/ansible-lint#2626
Fixes: #1026
Closes: #2593