Fix problem with runas failing to execute powershell scripts #61912
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.
What does this PR do?
Fixes the problem when specifying
runas
when running a powershell script.The issue was that the code that trying to escape characters by calling
win_functions.escape_argument
. However that function is for escaping characters for thecmd
shell, and in this case we are usingpowershell
to execute a script, and so powershell needs to know how to run the script. This is solved by prefixing the string with a&
, and surrounding it in quotes.What issues does this PR fix or reference?
Fixes: #61166
Previous Behavior
The output would appear something like this:
New Behavior
Script runs.