jscheffl commented on PR #65791: URL: https://github.com/apache/airflow/pull/65791#issuecomment-4319046822
> > Why would you want to override the ENV if there are specific helper template entries in the chart? > > Note that the full git sync mechanism will be dropped probably soon (plans will be dropped to devlist the next days). So as maintainer the motivation to add more complexity to a future legacy is a bit low. > > In my case, I retrieve the configuration for GitSync via Azure Key Vault and install the Helm chart via FluxCD – so I have an `externalSecret` that I now can reference in the Airflow chart to set the GitSync variables. The current implementation only allows customisation via `values.yaml`. Maintenance via `gitSync.env` is not possible due to the duplicate error. If you say that this feature will be removed soon, what would be the alternative? Will it still be possible to retrieve the DAG configuration via Git? > > @jscheffl Plan is to fully switch to Dag Bundles in the configuration. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
