[bitnami/airflow] Airflow container errors out if AIRFLOW_FERNET_KEY or AIRFLOW_SECRET_KEY start with a dash
#65197
Assignees
Labels
airflow
solved
stale
15 days without activity
tech-issues
The user has a technical issue about an application
Comments
zanecodes
added
the
tech-issues
javsalgar
changed the title
AIRFLOW_FERNET_KEY or AIRFLOW_SECRET_KEY start with a dashAIRFLOW_FERNET_KEY or AIRFLOW_SECRET_KEY start with a dash
|
Hi @zanecodes, Thank you for taking the time to create this ticket. If you have tried the change you proposed, would you like to contribute? You can follow our contributing guidelines and the whole community will benefit from your change. Thanks |
|
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Name and Version
bitnami/airflow:latest (currently 2.9.0-debian-12-r1)
What architecture are you using?
amd64
What steps will reproduce the bug?
Run
docker run -e 'AIRFLOW_SECRET_KEY=--PjzohgYFtiYCQjlyDNdeQdAIhXWgIAsE7Z-cMt7mg=' bitnami/airflow:2.7.3-debian-11-r2What is the expected behavior?
The container should correctly populate the
secret_keyconfiguration key under the[webserver]section in/opt/bitnami/airflow/airflow.cfgwith the value provided in theAIRFLOW_SECRET_KEYenvironment variable.What do you see instead?
The container setup script throws the error
expected argument for flag '-v, --value', but got option '--PjzohgYFtiYCQjlyDNdeQdAIhXWgIAsE7Z-cMt7mg='while creating the default configuration file.Additional information
This happens because the
airflow_conf_setfunction in/opt/bitnami/scripts/libairflow.shpasses the configuration value toini-fileas a separate argument.The issue can be fixed by changing the above-linked line to
ini-file set "--section=$section" "--key=$key" "--value=$value" -- "$file".This affects all configuration values that are written using
airflow_conf_set, namely:AIRFLOW_HOSTNAME_CALLABLEAIRFLOW_WEBSERVER_PORT_NUMBERAIRFLOW_FERNET_KEYAIRFLOW_SECRET_KEYAIRFLOW_EXECUTORAIRFLOW_BASE_URLValues starting with dashes are not valid for most of these anyway, but are valid for
AIRFLOW_FERNET_KEYandAIRFLOW_SECRET_KEY, and are indeed somewhat likely to occur since these are both URL-safe base64 encoded random byte sequences.The text was updated successfully, but these errors were encountered: