Sasha (Alejandro Vicente Grabovetsky)

A native way of having runtime environmental variables would be very helpful when deploying in Dockerised environments (e.g. Kubernetes) and following a 12-factor app approach, specifically https://12factor.net/build-release-run

I have the very same issue with the configuration file. The headings are nice, but documentation inside disappears. My objects are exported classes. Thanks in advance for looking into this!

I've also tried to recreate one of the tests in the __test__ suite of documentation, involving: ``` test('config with nested sections', async function() { var file = path.join(__dirname, 'fixture', 'sections.input.js');...

Actually, this may be to some extent bypassed by this example: https://github.com/simple-statistics/docs/blob/gh-pages/documentation.yml Still, the documentation of documentation, and the tests should be updated to reflect this possibility. But the "children"...

And updating charts with auto-generated passwords as discussed in Helm call and on this issue: helm/charts#5167

This is indeed a problem. Currently I'm overcoming this by specifying a value with ```--set``` flag to override sensitive information (e.g. passwords) during the upgrade process. I tend to save...

e.g. it could be useful to add an annotation that prevents updating of a secret like this: ``` "helm.sh/resource-policy": keep ``` Except this only works for preventing deletion.

@michaelfig I like this, either we explicitly specify the password, or we autogenerate it during an install. Does this work? (i.e. Have you tried running this to check that it...

Tried it myself just now, alas Helm will simply wipe out the secret.

Is there any progress on setting up a way for random secrets to not be reset implicitly during upgrades?