We have no specific work in progress at the moment, but we are actively listening in this area. Please continue to share specific scenarios.
364 votesUnder Consideration · 40 comments · Product Feedback » Deployments · Flag idea as inappropriate… · Admin →
An error occurred while saving the commentKenneth Larsen commented
Find this very relevant if you have helm charts that import files to be used as secrets or configmaps as documented here: https://helm.sh/docs/chart_template_guide/accessing_files/#configmap-and-secrets-utility-functions
In these cases the current functionality with replacement in the value(s) file(s) is not sufficient.
We use this pattern to avoid having a "bloated" values.yaml file, and furthermore having to overwrite the values in the config files that shouldn't change during deployment. You may have a config file with 100+ lines where you only wish to substitute very few variables.