You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "cjj1120 (via GitHub)" <gi...@apache.org> on 2025/06/18 02:34:45 UTC
[D] Issue: applyCustomEnv in migrateDatabaseJob with ArgoCD [airflow]
GitHub user cjj1120 created a discussion: Issue: applyCustomEnv in migrateDatabaseJob with ArgoCD
I'm trying to pass environment variables to the `migrateDatabaseJob` in order to enable logging features provided by my cloud provider.
After reviewing the Helm chart, it seems that the only way to inject custom environment variables is by setting `applyCustomEnv: true` under the `migrateDatabaseJob` section.
However, the [official Airflow Helm chart documentation](https://airflow.apache.org/docs/helm-chart/stable/index.html#installing-the-chart-with-argo-cd-flux-rancher-or-terraform) recommends setting the following configuration to false when using ArgoCD:
```
createUserJob:
useHelmHooks: false
applyCustomEnv: false
migrateDatabaseJob:
useHelmHooks: false
applyCustomEnv: false
```
I'm trying to understand why applyCustomEnv must be disabled in this context. The documentation doesn’t explain the reason behind this recommendation, and it’s unclear how enabling it might interfere with ArgoCD.
### What I've tried
- Manually triggered a sync from ArgoCD.
- Triggered a deployment from GitHub Actions.
In both cases, the deployment worked as expected with `applyCustomEnv: true`.
### Question
Is there a specific reason why the documentation advises setting `applyCustomEnv: false` when using ArgoCD? Could this be a precaution for compatibility, or have I possibly misunderstood the intent of the documentation?
GitHub link: https://github.com/apache/airflow/discussions/51862
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org