-
Notifications
You must be signed in to change notification settings - Fork 90
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
openssh_* modules: check return code on ssh(-keygen) invocations; fail if comment cannot be updated #646
Conversation
…and module is not in check mode.
On CentOS 6, comment change fails because of the |
The |
This was silently ignored in the past.
I think this is working now. Please ignore the failing FreeBSD CI jobs, the failures are completely unrelated (and happen in other repos as well). |
Please note that this might also start reporting errors in other cases that worked before (or looked like working - whether it's an error now reported or a wrongly reported error needs to be determined on a case-by-case basis). |
I'm okay with the module explicitly reporting errors rather than silently continuing. These changes were not made previously to avoid breaking behavior post-refactor. Also the idea at the time was to eventually deprecate/remove the |
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.
LGTM
Makes total sense. I've been thinking a bit about it while working on this PR, especially whether this is more a feature (the user should know if something doesn't work) or a breaking change. I guess it is both, but I think it's more a feature, so I added a
Yes, unfortunately... At least it's not as messy as GnuPG handling... ;-) |
@Ajpantuso thanks a lot for reviewing this! |
SUMMARY
Fixes #645.
ISSUE TYPE
COMPONENT NAME
openssh_cert
openssh_keygen