WinRM parameter passing fails for larger scripts #5538
Merged
Conversation
This file contains hidden or 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
pull-request-size
bot
added
the
size/XS
pull-request-size
bot
added
size/S
amanda11
reviewed
Feb 11, 2022
amanda11
approved these changes
Feb 16, 2022
Contributor
amanda11
left a comment
amanda11
left a comment
There was a problem hiding this comment.
LGTM - thanks for contribution.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
When winrm-ps-script runner type was used, found that we were unable to pass parameters successfully from Stackstorm to the PowerShell script. We noticed inconsistent parameter passing to the PowerShell scripts, seemingly being able to pass inputs to smaller scripts but not to larger ones.