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

Error: parse failed --exclude duplicated #255

Open
mutoo opened this issue Feb 18, 2020 · 3 comments
Open

Error: parse failed --exclude duplicated #255

mutoo opened this issue Feb 18, 2020 · 3 comments

Comments

@mutoo
Copy link

mutoo commented Feb 18, 2020

I was trying to list the files in the bucket with multiple exclusion filters.

It should be allowed as it's mentioned in the documentation:
https://github.com/aliyun/aliyun-cli/blob/master/oss/lib/ls.go#L44

--include和--exclude可以出现多次。当多个规则出现时,这些规则按从左往右的顺序应用

But it outputs an error saying: "--exclude duplicated"

  • Command Format:
$ aliyun oss ls oss://my-bucket/ --exclude "*.png" --exclude "*.jpg"
  • Output:
ERROR: parse failed --exclude duplicated
@night556
Copy link
Member

night556 commented Mar 4, 2020

I was trying to list the files in the bucket with multiple exclusion filters.

It should be allowed as it's mentioned in the documentation:
https://github.com/aliyun/aliyun-cli/blob/master/oss/lib/ls.go#L44

--include和--exclude可以出现多次。当多个规则出现时,这些规则按从左往右的顺序应用

But it outputs an error saying: "--exclude duplicated"

  • Command Format:
$ aliyun oss ls oss://my-bucket/ --exclude "*.png" --exclude "*.jpg"
  • Output:
ERROR: parse failed --exclude duplicated

Thank you for your Tssue. For some reasons, the CLI's support for OSS's flag is not perfect. Sorry for the problem. We will record the problem and fix it.

@bcuicn
Copy link

bcuicn commented Dec 21, 2020

Do you have any timeline on when this can be fixed?

@AndreasRIHU
Copy link

I would like to emphasize the importance of this issue to be fixed.
I'm currently porting our workflow from AWS to Alibaba Cloud and this issue is quite annoying,
because I can't use a lot of my scripts which use multiple --exclude's quite often...
And changing them isn't an option because it's an error that should work according to the docs.
Do you see any chance to accelerate resolving that issue?
And/Or: what is the time frame for "next-major-version"?
Best regards
Andreas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants