You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Helm charts for deis will produce different manifest files each time they are run (actually, each time generate is run). Some situations may dictate that the manifests be reproducible.
Likewise, the reason for this is that many templates generate random secrets. Some may prefer to not have random secrets, but to supply their own.
The solution seems to be to simply support template variables for the params that currently allow only generated ones.
That would allow people to supply values via a TOML/YAML/JSON file like we do with the object storage stuff, but would default back to a randomly generated password otherwise.
The text was updated successfully, but these errors were encountered:
This is particularly important if the Workflow install has to be recovered from backups. Controller to database username/password, and builder ssh key (once that moves to secret) at the very least.
Any thoughts on being able to dump a "values" file to hold the results of randomly generated values?
this has since been implemented, because templates cannot be overwritten unless you supply -f when running helm generate to prevent overwriting those files.
The current Helm charts for deis will produce different manifest files each time they are run (actually, each time
generate
is run). Some situations may dictate that the manifests be reproducible.Likewise, the reason for this is that many templates generate random secrets. Some may prefer to not have random secrets, but to supply their own.
The solution seems to be to simply support template variables for the params that currently allow only generated ones.
That would allow people to supply values via a TOML/YAML/JSON file like we do with the object storage stuff, but would default back to a randomly generated password otherwise.
The text was updated successfully, but these errors were encountered: