NoLogPasswordsRule: catch password_lock false positives and migrate tests #1562
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't trigger
no-log-password
whenpassword_lock
(https://docs.ansible.com/ansible/latest/collections/ansible/builtin/user_module.html#parameter-password_lock) is used and thepassword
parameter isn't.It will trigger when both
password
andpassword_lock
is used.Migrate the tests from separate files in
examples/
andtest/
intosrc/ansiblelint/rules/NoLogPasswordsRule.py
.Signed-off-by: Thomas Sjögren [email protected]