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
I had searched in the issues and found no similar feature requirement.
Use case
running the devlake part (not config-ui, not grafana) we need to ingest the value of DB_URL (either from .env file or as environment variable) in order to set up the mysql connection
sadly this contains the full connection string
Usually (like for grafana and opendora) the connection is set up via DB_HOSTNAME, DB_USER, DB_PASSWORD, DB_NAME as environment variables that make us able to put DB_PASSWORD into an encrypted vault.
With the given solution above we need to create the connection string and store all data in a vault. Additionally it needs to be recreated on password reset.
Description
I suggest to use DB_HOSTNAME, DB_USER, DB_PASSWORD, DB_NAME for the database connection setup instead of DB_URL.
This makes us able to store DB_PASSWORD in an encrypted vault and rotate only that vault/value on password rotation.
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
Search before asking
Use case
running the devlake part (not config-ui, not grafana) we need to ingest the value of DB_URL (either from .env file or as environment variable) in order to set up the mysql connection
sadly this contains the full connection string
see https://github.com/apache/incubator-devlake/blob/main/env.example#L26
Usually (like for grafana and opendora) the connection is set up via DB_HOSTNAME, DB_USER, DB_PASSWORD, DB_NAME as environment variables that make us able to put DB_PASSWORD into an encrypted vault.
With the given solution above we need to create the connection string and store all data in a vault. Additionally it needs to be recreated on password reset.
Description
I suggest to use DB_HOSTNAME, DB_USER, DB_PASSWORD, DB_NAME for the database connection setup instead of DB_URL.
This makes us able to store DB_PASSWORD in an encrypted vault and rotate only that vault/value on password rotation.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: