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

rhg_compute_tools.gcs.cp might not always do what we expect #86

Open
bolliger32 opened this issue Aug 28, 2020 · 2 comments
Open

rhg_compute_tools.gcs.cp might not always do what we expect #86

bolliger32 opened this issue Aug 28, 2020 · 2 comments

Comments

@bolliger32
Copy link
Collaborator

I'm not 100% positive I wrote the cp command correctly to handle cases where you are copying directories to other directories. The rules for exactly how the copy is conducted, depending on whether or not you specify -r, whether you are using single or double wildcard characters, and whether you are copying files or directories, are quite complicated. It's making my head spin and so I gave up trying to fix things for now. sync is often a simpler and easier option b/c you know you are syncing a directory to a directory. But at some point, we should take a look at cp and make sure it's working appropriately.

@brews
Copy link
Member

brews commented Aug 28, 2020

Can you outline the behavior we want for rhg_compute_tools.gcs.cp with some concrete examples here, @bolliger32?

@bolliger32
Copy link
Collaborator Author

Yeah, will do when I get some time. In general, the way the others work is to first call the appropriate gsutil command and then create all the necessary directories in gcsfuse so that you are actually able to see the files (b/c gsutil won't do that). It's just a little more complicated with cp than with sync b/c you could be copying either folders or files and you can use wildcards, etc. I'll put some examples up when i get a chance

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

2 participants