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
pmrun.py: Recreate the older behavior where the entire success command was quoted #66929
Conversation
Switching to shlex_quote the output is now identical to what was produced under 2.7.x |
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.
Change looks good. Just needs a changelog fragment. See this fragment as an example.
@lotaris-xx this PR contains the following merge commits: Please rebase your branch to remove these commits. |
Added. Thanks, |
ready_for_review |
Please create a backport PR for this to be included in previous versions. |
…ccess command was quoted (#67241) * pmrun - quote success command (#66929) * Recreate the older behavior where the entire success command was quoted * Use shlex_quote for a correct fix of this * Add changelog fragment (cherry picked from commit fd8eb77) * Backport of 66929-pmrun-quote-entire-success-command-string * Update changelog fragment * Delete 66929-pmrun-quote-entire-success-command-string.yml Unclear from docs, but this is the devel fragment so removing. * Update changelog
SUMMARY
Adds a set of quotes around the entire success command. This was the behaviour back in the 2.7.x days. Have a client using pmrun that is blocked from upgrading to current ansible by this.
The original change that removed the "extra" quotes caused a regression. I don't see how adding these back in would break anything for the few pmrun users out there.
I'm setting this as a bugfix as it is a regression for an actual user of this plugin, but if that isn't appropriate please let me know.
ISSUE TYPE
COMPONENT NAME
pmrun.py
ADDITIONAL INFORMATION
Before Change:
After Change:
2.7.x behaviour: