darkoperator / darkoperator/Posh-SSH
Set-SCPFile - Different Destination Filename
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
In version 1.7: "On Set-SCPFile the parameter RemoteFile is now changed to RemotePath and one only needs to give the Path to where to copy the file."
A consequence of this change is that if you want the destination filename to differ from the source, you now have to copy the file and then rename it. This extra step is time consuming when dealing with large numbers of files.
Would it be possible to reinstate the ability to specify a different destination file name?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Set-SCPFile implementation and its handling of the RemotePath parameter. Determine how a separate destination filename could be specified without requiring a copy-and-rename step, then verify that files can be transferred under a different remote name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100