You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cp command's -R option works on local files (as source) only. When downloading, if there's a wildcard it's always recursive so there's no real need for an -R option. Maybe add a dummy/no-op -R option to "from-remote" cp command?
Currently having the -R in an s3-sourced cp command fails with the confusing error message "File param resembles s3 object", as it parses the command as having a local source. (since -R is not an option for remote sourced files)
Another fix would be to reverse the parsing order so that arguments get parsed first, options later. Since s3 urls are expected to always start with s3:// scheme, it would select the correct command and fail with an "no such option" error message which is much clear.
The text was updated successfully, but these errors were encountered:
Local copy support is dropped as of v1.0.0 release. -R flag is gone as well because of the above reason. It doesn't have any effect other than local->local copy operations.
cp command's
-R
option works on local files (as source) only. When downloading, if there's a wildcard it's always recursive so there's no real need for an -R option. Maybe add a dummy/no-op -R option to "from-remote" cp command?Currently having the -R in an s3-sourced cp command fails with the confusing error message "File param resembles s3 object", as it parses the command as having a local source. (since -R is not an option for remote sourced files)
Another fix would be to reverse the parsing order so that arguments get parsed first, options later. Since s3 urls are expected to always start with
s3://
scheme, it would select the correct command and fail with an "no such option" error message which is much clear.The text was updated successfully, but these errors were encountered: