You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:18:36 UTC
Re: [D] Using env vars in the extraConfigs / import_datasources.yaml part of the helm chart [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Using env vars in the extraConfigs / import_datasources.yaml part of the helm chart
<!-- Greeting -->
Hello @cyber-cricket! I'm [Dosu](https://dosu.dev), here to help you with bugs, answer questions, and guide you in becoming a contributor. I'll be waiting alongside you for a human maintainer to jump in!
<!-- Answer -->
I couldn't find specific documentation or examples in the Superset Helm chart repository that demonstrate using environment variables directly within the `import_datasources.yaml` file. However, the Helm chart does support the use of environment variables in general through the `extraEnv`, `extraEnvRaw`, and `extraSecretEnv` sections in the `values.yaml` file, which are used to set environment variables in the Superset pod's container <sup>[[1]](https://github.com/apache/superset/blob/master/helm/superset/values.yaml)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/helm/superset/templates/deployment.yaml)</sup>.
For dynamic configuration using environment variables, you might consider using a custom script or entrypoint that processes the `import_datasources.yaml` file before it is used by Superset. This script could replace placeholders in the YAML file with actual environment variable values from the container.
If you need to use environment variables in configuration files like `import_datasources.yaml`, you might need to preprocess these files with a script that substitutes environment variables before they are consumed by Superset. This approach isn't directly supported by the Helm chart but can be implemented as part of your deployment process.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=61586b05-1f95-4337-933e-ca73841d2127) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33379#discussioncomment-13053631
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org