win_powershell - support scripts with 7 syntax #459
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
jborean93
force-pushed
the
powershell-pwsh7
branch
from
03acb2e
to
0db5aec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
It is possible to use PowerShell 7 scripts with this module when
executable: pwsh.exeis used. This means the scriptblock parser that is being used will fail in Windows PowerShell when encountering syntax added in 7. This adds a fallback to using a regex match to check if the script also containsSupportsShouldProcess.Fixes: #452
ISSUE TYPE
COMPONENT NAME
win_powershell