A question on how this should be implemented: Should the app.ini file be left completely alone after it is first created, or should certain values such as the postgres password (as was present previously) and other configuration options that are set in values.yaml for the app.ini file be updated as well on helm install and helm upgrade? It becomes a tedious task to manually update values present in values.yaml within the app.ini file otherwise.
Would you accept a PR for mariadb password upgrade if app.ini exists? It would be possible to upgrade helm and keep the password in k8s secrets instead of hardcoding the password in values.yaml.
Reintroduce app.ini persistence per issue #38.
A question on how this should be implemented: Should the app.ini file be left completely alone after it is first created, or should certain values such as the postgres password (as was present previously) and other configuration options that are set in values.yaml for the app.ini file be updated as well on
helm install
andhelm upgrade
? It becomes a tedious task to manually update values present in values.yaml within the app.ini file otherwise.