Hi everyone! 👋 I was browsing the Helm plugin directory and saw something called `helm-values-from-db`. It claims to pull configuration values from external databases like PostgreSQL or MySQL and inject them into Helm releases.
As someone still getting comfortable with Helm, I'm really curious if anyone has tried this in production? My main questions:
- How does it handle secrets securely? I saw it can use environment variables, but is that enough?
- Does it add significant complexity to the deployment pipeline?
I tried a basic test locally with a dummy table:
```yaml
# values.yaml
databasePlugin:
enabled: true
connection: "$DB_CONN_STRING"
query: "SELECT key, value FROM config WHERE environment = 'staging'"
```
But I'm not sure about the best practices here. Any experiences or warnings would be super helpful! 😅
Oh cool, I just started using Helm for a small project and hadn't seen this plugin. Thanks for mentioning it!
I'm also worried about the secrets part. Using environment variables feels okay, but I'd be scared of that connection string leaking into logs somewhere during the plugin's process. Maybe someone who's used it can explain how they lock that down.
You said you ran a basic test locally? Did it just spit the values straight into your final helm template, or was there an extra validation step? I'm wondering how you catch a bad query result before it deploys.
Ask me in a year