{Core} Entry script: Use @args
to tolerate incorrectly passing list with $
#23802
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.
Close #23797
#23514 changed the entry script
az.cmd
toaz.ps1
when executed in PowerShell.Consider we have an array
Some user passes the array to
az.ps1
as$mylist
:This is incorrect, as
$args
will become an array of array. Using$args
to call a native exe will only splat the outer array and concatenate the inner array's items.The correct way to a pass a list to
az
is to pass space-separated arguments, so in PowerShell, user should use@
splatting when callingaz.ps1
:Meanwhile, when calling native exe with
@args
, it will even splat internal arrays. We can use a test scripttest.ps1
to verify this behavior:Interesting thing is that even
@args
can only splat 2 layers and the 3rd layer was concatenated:We can go even deeper: