Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Environment variables reference

See original GitHub issue

Hello,

I think it’s worth creating a list of environment variables used by Airflow. This will allow you to refer to it from other places in the documentation. We should use envvar directive in this docs.

This list can be added to the file: docs/cli-ref.rst (preview)

We have the following environment variables

.. envvar:: AIRFLOW__{SECTION}__{KEY}
.. envvar:: AIRFLOW__{SECTION}__{KEY}_CMD
.. envvar:: AIRFLOW_CONFIG
.. envvar:: AIRFLOW_CONN_{CONN_ID}
.. envvar:: AIRFLOW_HOME
.. envvar:: AIRFLOW_VAR_{KEY}

We can be inspired by the following links https://docs.docker.com/compose/reference/envvars/ https://raw.githubusercontent.com/python/cpython/7864f11cdf12807555d62c7a132c191eb41ecc02/Doc/using/cmdline.rst https://docs.python.org/3/using/cmdline.html#envvar-PYTHONPATH

If anyone is interested in this, I am willing to provide all the necessary tips and information.

Are you wondering how to start contributing to this project? Start by reading our contributor guide

Best regards, Kamil

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:8 (7 by maintainers)

Top GitHub Comments

3reactions

faihegbergcommented, Sep 12, 2020

@mik-laj I’d like to grab this one if that’s ok 🙂 I just finished reading through the contribution guideline/documentation and this will be my first issue. Please let me know if you have any additional info that you think will be helpful.

1reaction

mik-lajcommented, Nov 22, 2020

@gflores1023 If you want to propose a change then you don’t have a ticket. It is enough to create a PR.