When developing features, you may need to persist information to the metadata database. Airflow has Alembic built-in module to handle all schema changes. Alembic must be installed on your development machine before continuing with migration. If you had made changes to the ORM, you will need to generate a new migration file. This file will contain the changes to the database schema that you have made. To generate a new migration file, run the following:
# starting at the root of the project
$ breeze --backend postgres
$ cd airflow
$ alembic revision -m "add new field to db" --autogenerate
Generating
~/airflow/airflow/migrations/versions/a1e23c41f123_add_new_field_to_db.pyNote that migration file names are standardized by pre-commit hook update-migration-references, so that they sort alphabetically and indicate
the Airflow version in which they first appear (the alembic revision ID is removed). As a result you should expect to see a pre-commit failure
on the first attempt. Just stage the modified file and commit again
(or run the hook manually before committing).
After your new migration file is run through pre-commit it will look like this:
1234_A_B_C_add_new_field_to_db.py
This represents that your migration is the 1234th migration and expected for release in Airflow version A.B.C.
You can also learn how to setup your Node environment if you want to develop Airflow UI.