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

Replace * value with other more bash friendly value #5963

Open
nflaig opened this issue Sep 18, 2023 · 9 comments
Open

Replace * value with other more bash friendly value #5963

nflaig opened this issue Sep 18, 2023 · 9 comments
Labels
good first issue Issues that are suitable for first-time contributors. meta-feature-request Issues to track feature requests.
Milestone

Comments

@nflaig
Copy link
Member

nflaig commented Sep 18, 2023

Problem description

* is not very friendly to use in bash, it has to be quoted or else it will not be handled as a string but an operator instead, i.e. it will list all files of the directory.

There are currently a few CLI flags that accept * as a value

  • --rest.namespace
  • --rest.cors
  • --keymanager.cors

See Command Line Reference for an overview of all non-hidden flags.

Solution description

Replace * value with other more bash friendly value, for example the word all.

It has to be considered what value to use for cors as * has a special meaning in this context.

Additional context

No response

@nflaig nflaig added the meta-feature-request Issues to track feature requests. label Sep 18, 2023
@nflaig nflaig added the good first issue Issues that are suitable for first-time contributors. label Oct 18, 2023
@clionachee
Copy link

Hi, may I know specifically which file or all the files? Is this issue still needing to be resolved?

@nflaig
Copy link
Member Author

nflaig commented Feb 19, 2024

Hey, there are multiple cases but likely just wanna change this for --rest.namespace (see related PR #2809), and make sure it's backward compatible, i.e. * should still be handled if passed by the user.

It is probably also the only place where we would wanna change this, as for .cors CLI flags, the * has special meaning, and we can't change it to something like "all" there as it might be confusing.

@clionachee
Copy link

Thanks. I suppose if it's ok, I'll fork the Repo, make the changes in that file, replace the value & commit changes if no problem?

@nflaig
Copy link
Member Author

nflaig commented Feb 20, 2024

Sure, go ahead, you can open a PR here after you are done with your changes. Happy to review :)

@clionachee
Copy link

clionachee commented Feb 20, 2024

Created PR #6459 thanks w/ love.

@philknows
Copy link
Member

#7011 target

@philknows philknows added this to the v2.0.0 milestone Oct 22, 2024
@nflaig
Copy link
Member Author

nflaig commented Oct 22, 2024

011 target

we should add this in a backward compatible way

@eenagy
Copy link

eenagy commented Oct 30, 2024

Can we have proper quoting instead of replacing it? ex: --rest.namespace '*' and so on.

@nflaig
Copy link
Member Author

nflaig commented Oct 30, 2024

Can we have proper quoting instead of replacing it? ex: --rest.namespace '*' and so on.

Yes, you have to quote it otherwise it won't work, that's why we wanna replace it with a more bash friendly value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Issues that are suitable for first-time contributors. meta-feature-request Issues to track feature requests.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants