dstandish edited a comment on issue #16684: URL: https://github.com/apache/airflow/issues/16684#issuecomment-942772689
I too see the value in allowing components of the `standard_airflow_environment` to be sourced in a way other than k8s secret. One reason is, if it's an officially supported way of managing configuration in airflow, then the helm chart should probably allow it. Otherwise it's confusing, as a user sees "oh i can store these params in AWS ssm" only to later discover it's not possible with the helm chart. Another reason is the convenience of managing everything from one source. Rather than some things in k8s secrets, others in vault or SSM -- better to have one place. And from a CI perspective, managing k8s secrets can be a little more cumbersome than something like vault or SSM. From an implementation perspective, it seems we might be able to just move everything to `extraEnvFrom` (or something like this), and get rid of the `standard_airflow_environment` e.g. and the similar celery one. Then the user has the flexibility afforded by airflow. -- 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]
