Table of Contents generated with DocToc
Date: 2022-01-29
Accepted
Airflow breeze can use different backends as metadata db and those
backends are run as separate containers, and enabled via the
--backend switch when running Breeze. Those databases
store their database files locally in container normally, which means
that when the database container is stopped, the database is gone.
While this is convenient for development to start from scratch, there is often a need to keep the data in the database across DB container restarts. This can be achieved by having volumes.
On the other hand, we want to have possibility of wiping out the environment totally - with removing all the database data. This is especially useful when you switch branches and the structure of the DB you locally have is newer than the structure your code is aware of.
Each Breeze's backend (including SQLite for consistency) stores
their database files in a volume created automatically when
appropriate --backend flag is used. This is done in
backend-<BACKEND>.yml docker-compose file.
This volume stays until it is manually deleted or until
breeze down command is called. The breeze down command
stops all the containers and removes all the volumes, in order
to provide an easy way to start breeze environment from
scratch.
Developers who need to restart their database will be able to do it without losing the database data. However, there is also an easy way to drop and recreate the databases from the scratch.