-
Notifications
You must be signed in to change notification settings - Fork 403
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
ses: fix clearing notification topic #1730
ses: fix clearing notification topic #1730
Conversation
Build failed. ❌ ansible-galaxy-importer FAILURE in 4m 04s |
I don't know what is causing the |
recheck |
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.
Thanks for taking the time to submit this PR. I'm a little concerned about how this change behaves. As it is today this has the potential to wipe out configuration that people expect to still be there.
Build failed. ❌ ansible-galaxy-importer FAILURE in 3m 50s |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 47s |
f146499
to
d46cf46
Compare
Thanks for your work on this, I'm sorry it's taken a while to get back to you. I've just pushed two minor tweaks, the first is just a minor formatting thing, we're starting to use darker/black to make our formatting more consistent. The second changed the "parameter not passed" logic slightly. Top level parameters will always be in "params", if they were omitted in the task then they show up as |
regate |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 4m 43s |
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
SUMMARY
Fixes #150. As per the docs, the
SnsTopic
parameter has to be omitted from the request in order to clear the notification setting.ISSUE TYPE
COMPONENT NAME
ses_identity