2146940 Fix AzureFileCopyv6 task to support PowerShell 7.4.x version #19827
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
manolerazvan
approved these changes
Apr 30, 2024
|
/azp run |
|
Azure Pipelines failed to run 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
PhilipsonJoseph
approved these changes
Apr 30, 2024
7 tasks
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.
Task name: AzureFileCopyV6
Description: While using Power shell core we used to see error on InvokeVsts-tool function on latest power shell. To solve it updated the vstsSDK and use InvokeVSTS-process
Bug 2146940: Fix AzurePowersShell task to support PowerShell 7.4.x version
Removed SASToken for VM Copy.
Documentation changes required: (Y/N) N
Added unit tests: N
Attached related issue: Y
Checklist: