win_regedit: fix extra info coming into stdout #31813
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 16, 2017
ansibot
added
affects_2.5
jborean93
removed
the
needs_triage
|
Ha, that totally makes sense. Thanks for tracking it down, I'll try it out later this week hopefully. |
abadger
moved this from TODO: Nice to have
to To be cherrypicked (rc only)
in 2.4.x Blocker List
abadger
pushed a commit
that referenced
this pull request
Oct 18, 2017
(cherry picked from commit 888de84)
|
cherry-picked for 2.4.1rc2 |
abadger
moved this from To be cherrypicked (rc only)
to Done in 2.4.1
in 2.4.x Blocker List
This was referenced Jan 31, 2018
ansibot
added
bug
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
New-ItemandRemove-Itemoutput into which eventually ends up in the stdout stream sent back to Ansible. Usually this isn't an issue as Ansible parses the output from when it first detects{but in the case of the property of data containg that character (like a guid of json string), Ansible won't be able to parse the output and it fails even though it really didn'tThis change makes sure that extra data is not sent to the output/stdout stream so Ansible won't get confused in the end.
fixes #31423
fixes #31782
ISSUE TYPE
COMPONENT NAME
win_regedit
ANSIBLE VERSION