Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rsync as a kubectl cp replacement struggles with destination folders #225

Open
stmh opened this issue Feb 8, 2022 · 0 comments
Open

rsync as a kubectl cp replacement struggles with destination folders #225

stmh opened this issue Feb 8, 2022 · 0 comments
Assignees
Milestone

Comments

@stmh
Copy link
Member

stmh commented Feb 8, 2022

The current implementation of using rsync as a replacement for kubectl cp does not respect the destination folder/ file-name. It will create the file in the current working directory with the same name as the uploaded file. Either find a solution to remane that file via rsync or move the file to the correct place after rsyncing it.

@stmh stmh added this to the 3.8.0 milestone Feb 8, 2022
@stmh stmh self-assigned this Feb 8, 2022
@stmh stmh changed the title rsync as a kubectl cp replacement stuggles with dstination folders rsync as a kubectl cp replacement struggles with destination folders Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant