-
Notifications
You must be signed in to change notification settings - Fork 23.8k
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
no_log even when task_result doesn't provide key #41414
Conversation
- now also checks task property - added reproducer to tests for unreachable status on item loop
insertafter: EOF | ||
line: "machine {{ item.machine }} login {{ item.login }} password {{ item.password }}" | ||
loop: "{{ logins }}" | ||
no_log: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should there be an assert that checks that DO_NOT_LOG_UNREACHABLE_ITEM
is not in the output of the task somehow ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in runme.sh, it was already part of existing tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, gotcha.
+1 to merge |
Also needs backporting to stable-2.6, stable-2.5 and stable-2.4 |
Hmm,.. this does need a change log fragment, though. (Which will make backporting to 2.6 and 2.5 easier but will have to be changed for 2.4) |
The unstable test result is unrelated merging and openin backports. |
SUMMARY
ISSUE TYPE
COMPONENT NAME
task result
ANSIBLE VERSION