-
Notifications
You must be signed in to change notification settings - Fork 398
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
Make iam module more predictable and idempotent … #369
Make iam module more predictable and idempotent … #369
Conversation
…_name it creates/deletes
@stefanhorning thank you for the PR. Could you add changelog fragment? |
@gravesm done. |
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.
The PR/Issue should be linked to in the changelog fragment, this helps folks digging into changes that might have introduced bugs or behaviour changes.
I would generally say that idempotency is more about a lack of "changed" (and not actually making a change) rather than a different return value.
Thanks for your PR. I'm sorry it's taking so long to get through these reviews. Just a minor niggle |
Co-authored-by: Mark Chappell <[email protected]>
@tremble done |
Thanks @stefanhorning |
…s#369) * Make iam module more predictable and idempotent on returning the user_name it creates/deletes * Add changelog fragment for iam module change
…s#369) * Make iam module more predictable and idempotent on returning the user_name it creates/deletes * Add changelog fragment for iam module change
…s#369) * Make iam module more predictable and idempotent on returning the user_name it creates/deletes * Add changelog fragment for iam module change
…ections#369) Update README with new python and botocore requirements Reviewed-by: https://github.com/apps/ansible-zuul
…on returning the user_name it creates/deletes
SUMMARY
Currently dependending on what the module does (create/update/delete) one has to find the returned user_name in different places (or it won't be returned at all). To make this behaviour more consistent, this patch makes sure that the user name is always returned under the
user_name
key.ISSUE TYPE
COMPONENT NAME
iam.py
ADDITIONAL INFORMATION
I have gist here with a playbook showcasing the issue: https://gist.github.com/stefanhorning/a948b9f63a5db8a2a38fc988080a13b2
Run it without my patch and you will get arbitrary output (defined/undefined) for the user_name param. Run it with my patch and it will behave predictably and consistent.