jedcunningham commented on issue #16684: URL: https://github.com/apache/airflow/issues/16684#issuecomment-872597711
Another option, granted with a little more complexity, is to have an init container be fully responsible for building a complete airflow.cfg, which Airflow then uses via the shared emptyDir. This would nicely separate the config stuff and Airflow, and hopefully is flexible enough to support other secret approaches too. Said another way, have the init container take the "base" airflow.cfg and inject (in the case of vault) stuff from /vault/secrets/* into a combined airflow.cfg. -- 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]
