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
if users are None/empty, dont assume sameness #58875
Conversation
We should probably extend the tests in |
and add clog, was just seeing if all current tests passed |
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.
We definitely need test cases for this. It's pretty hard to follow this logic even when it is broken out into a separate method.
(cherry picked from commit 4ef2545) also fix all cases of none remote/become users (ansible#59397) some cases failed, when defaults were None on the plugins (cherry picked from commit 74ac229)
prevents None == None cases in which 'defaults' for remote and become differ
ISSUE TYPE
COMPONENT NAME
actions