Sometimes you might want to update dependencies of airflow in bulk, when working on related set of packages/dependencies. This might lead to excessive time needed to rebuild the image with new versions of dependencies (due to pip backtracking) and necessity to rebuild the image multiple times and solving conflicting dependencies.

For development use only, you can store your own version of constraint files used during CI image build here and refer to them during building of the image using --airflow-constraints-location constraints/constraints.txt This allows you to iterate on dependencies without having to run --upgrade-to-newer-dependencies flag continuously.

Typical workflow in this case is:

• download and copy the constraint file to the folder (for example via The GitHub Raw Link
• modify the constraint file in “constraints” folder
• build the image using this command

breeze ci-image build --python 3.7 --airflow-constraints-location constraints/constraints-3.7txt

You can continue iterating and updating the constraint file (and rebuilding the image) while iterating, you can also manually add/update the dependencies and after you are done, you can regenerate the set of constraints based on your currently installed packages, using this command:

pip freeze | sort | \
    grep -v "apache_airflow" | \
    grep -v "apache-airflow==" | \
    grep -v "@" | \
    grep -v "/opt/airflow" > /opt/airflow/constraints/constraints-3.7.txt

If you are working with others on updating the dependencies, you can also commit the constraint file to the repository and then anyone else working on the same branch/fork, can use it for local image building (but the file should be removed before the branch you are working on is merged to the main branch).