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
Device and OS: App version: Kubernetes distro: Kubernetes version: provider:
When a config file contains a constants sub-key that is not all lowercase, and it's referenced in a case-senstive way, the templating render will fail
constants
e.g., lula-config.yaml
constants: myKey: some-value
ref.yaml
valueOfMyKey: {{ .const.myKey }}
lula tools template -f ref.yaml
valueOfMyKey: some-value
Error: executing "template" at <.const.myKey>: map has no entry for key "myKey" (because viper converts myKey -> mykey)
Associated Viper issue: spf13/viper#1014
The text was updated successfully, but these errors were encountered:
Discussed the options for handling case-sensitivity or debugging and error output.
Sorry, something went wrong.
No branches or pull requests
Environment
Device and OS:
App version:
Kubernetes distro:
Kubernetes version:
provider:
Steps to reproduce
When a config file contains a
constants
sub-key that is not all lowercase, and it's referenced in a case-senstive way, the templating render will faile.g., lula-config.yaml
ref.yaml
lula tools template -f ref.yaml
Expected result
Actual Result
Error: executing "template" at <.const.myKey>: map has no entry for key "myKey"
(because viper converts myKey -> mykey)
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
Associated Viper issue: spf13/viper#1014
The text was updated successfully, but these errors were encountered: