Environment variables and airflow.cfg mapping

[erosons]

@mb-m @thesuperzapper referencing readme https://github.com/airflow-helm/charts/blob/main/charts/airflow/docs/faq/configuration/airflow-configs.md

if an env is set say this use case AIRFLOW__WEBSERVER__WEB_SERVER_SSL_KEY from a Secret , does the airflow.cfg automatic detect the the env , I see the from docs. it says you can either set in the airflow.cfg or environment variables
image

My main concern I don't see theses env in list env in the web server pod, is this env hidden because of security, appreciate contributions.

image

[thesuperzapper]

@erosons It's just the way that airflow works. You can set configs with a combination of the airflow.cfg file AND/OR the environment variables, but they are not connected in and of themselves.

The chart uses environment variables because they trigger airflow to restart (and pick up the new configs) when the PodSpec's envFrom secret changes (we put a hash of the secret contents the Pod's annotations).

[erosons]

so basically this will be right format for to definition in the values.yaml for the hash to validate correctly , or is there a defacto fromat definition for the env in the values.yaml

airflow:
   extraEnvFrom:
     - name: AIRFLOW__WEBSERVER__WEB_SERVER_SSL_KEY
        valueFrom:
           secretKeyRef:
             name: web-cert-and-key
             key: server.key