GitHub user ytihianine created a discussion: Custom image and helm deployment
Hey, I am willing to build my own custom image and launch it using a helm
deployment.
Currently, my main goal is provide a default config in the image.
My Dockerfile has those line:
```
ARG SUPERSET_VERSION
ARG SUPERSET_REPO
FROM ${SUPERSET_REPO}:${SUPERSET_VERSION}
COPY --from=dsfr_image
/app/superset-dsfr/docker/pythonpath_dev/superset_config.py
/app/pythonpath/superset_config.py
```
My config has this line (simplified example):
```
# Specify the App icon
APP_ICON = "/static/assets/local/images/app_icon.png"
```
I am also doing other stuffs which work fine !
Building this image and launching it locally with a simple docker run works
without any issues.
However, when deploying with Helm using the guide provided in this repo
(official superset), my whole app/pythonpath folder is overrided by a template
function in the `_helpers.tpl` file : `{{- define "superset-config" }}` which
generate the default superset_config without the "import" step at the end.
I've tried to look for a way to disable this behaviour but did not find any :/
If anyone can help :pray:
GitHub link: https://github.com/apache/superset/discussions/34861
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to:
notifications-unsubscr...@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
