Repository navigation
Enable cross providers support #6586
Description
This is a feature request. Currently we do not have cross providers support in the pwsh. It can be useful for sceanrios like copy-item from a file handled by a filesystem provider and to the cloud storage or automation accounts etc, handled by SHiPS provider. For example,
PS Azure:\...\> Copy-Item C:\test\hi.ps1 .\MyRunbook
Copy-Item : Source and destination path did not resolve to the same provider.
At line:1 char:2
+ Copy-Item C:\test\hi.ps1 .\MyRunbook
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (System.Collecti...[System.String]:Collection`1) [Copy-Item], PSArgumentException
+ FullyQualifiedErrorId : CopyItemSourceAndDestinationNotSameProvider,Microsoft.PowerShell.Commands.CopyItemCommandSteps to reproduce
Expected behavior
Actual behavior
Environment data
> $PSVersionTable
Reacted by Michael Klement, Jared Lam, Jim Przybylinski, Dan Thompson, Patrick Meinecke and Tom Winter
Activity
BrucePay commentedon Apr 7, 2018
Note: this is something we talked about doing a long time ago. At the time there wasn't a compelling scenario: copying files to reg keys was about the best we had. Now with Azure, copying to and from various Azure (and other cloud) stores makes a lot of sense. It's probably time to take a serious look at doing this.
Rob-S commentedon Jan 6, 2020
Another use case would be copying backup files to Google Cloud:
Copy-Item -LiteralPath 'filesystem::C:\Backups\AdventureWorks2008R2.bak' -Destination 'gs:\my-gc-bucket\AdventureWorks2008R2.bak'
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.