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
Several services use the Management Portal Postgres database to store data (as opposed to each spinning up a dedicated database pod). At present the transfer of database connection settings (url, secrets, etc.) is needed from the Management Portal helmfile config to the other services.
It would be nice to refactor the helmfile values and secretes so that the database connection settings are defined as global parameters analogous to for instance server_name.
The text was updated successfully, but these errors were encountered:
We use managed AWS RDS and at present we use different user/pass for each database and hence cannot be shared. We would also like to keep the option open to use a different database instance (esp. for appserver). We can have a global common and keep the app specific ones too, then in the helmfiles we can use if/else to check if the app specific ones are configured. If not then it will use the common shared ones?
We can have a global common and keep the app specific ones too, then in the helmfiles we can use if/else to check if the app specific ones are configured.
Several services use the Management Portal Postgres database to store data (as opposed to each spinning up a dedicated database pod). At present the transfer of database connection settings (url, secrets, etc.) is needed from the Management Portal helmfile config to the other services.
It would be nice to refactor the helmfile values and secretes so that the database connection settings are defined as global parameters analogous to for instance server_name.
The text was updated successfully, but these errors were encountered: