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
A better approach would be to allow a single string to represent all three values, a so called DSN (at least that's a common name in Symfony ecosystem for this concept).
It makes this a single piece of data which is easier to manage as a secret (for example in k8s). This approach is very common otherwise, for example Symfony itself uses it for cache and messenger, Doctrine uses it for the DB connection string, etc.
Is your feature request related to a problem? (optional)
No response
Describe alternatives you've considered (optional)
You can store JSON in the secret and then unwrap it, but that's cumbersome to manage.
Additional context (optional)
In some cases, you're billed per secret used so keeping it all together reduces cost.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the new feature
Currently, the credentials are passed individually, like so
A better approach would be to allow a single string to represent all three values, a so called DSN (at least that's a common name in Symfony ecosystem for this concept).
Why?
It makes this a single piece of data which is easier to manage as a secret (for example in k8s). This approach is very common otherwise, for example Symfony itself uses it for cache and messenger, Doctrine uses it for the DB connection string, etc.
Is your feature request related to a problem? (optional)
No response
Describe alternatives you've considered (optional)
You can store JSON in the secret and then unwrap it, but that's cumbersome to manage.
Additional context (optional)
In some cases, you're billed per secret used so keeping it all together reduces cost.
The text was updated successfully, but these errors were encountered: