We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bug
I read the documentation.
Consistency.
Differences in CLI arguments.
In many places examples of uising the CLI use a different case for their arguments. For example, https://docs.traefik.io/https/acme/#dnschallenge says:
--certificatesResolvers.sample.acme.httpChallenge.entryPoint=web
But then the main page for all the arguments (https://docs.traefik.io/reference/static-configuration/cli/) says:
--certificatesresolvers.<name>.acme.httpchallenge.entrypoint
All lower case. Is there a semantic difference or do they both work? The logs don't say anything.
I'm using 2.0 GA from Kubernetes via the CRD.
The text was updated successfully, but these errors were encountered:
Hello,
The flags names are case insensitive, there is no semantic difference.
Sorry, something went wrong.
It is confusing to me but if that's what it is, then cool. I must have missed the documentation clarifying it.
Closed by #5428.
Cheers folks!
No branches or pull requests
Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?
What did you do?
I read the documentation.
What did you expect to see?
Consistency.
What did you see instead?
Differences in CLI arguments.
In many places examples of uising the CLI use a different case for their arguments.
For example, https://docs.traefik.io/https/acme/#dnschallenge says:
But then the main page for all the arguments (https://docs.traefik.io/reference/static-configuration/cli/) says:
All lower case. Is there a semantic difference or do they both work? The logs don't say anything.
I'm using 2.0 GA from Kubernetes via the CRD.
The text was updated successfully, but these errors were encountered: