Right now the path to the migrations only works if installed locally. This may not be a big issue though, if migrations are deployed the same way DAGs are (they could, I suppose reside just alongside them).
Seeing as normally the revs for migrations sit alongside application code that uses it, how would those kind of migrations be pushed to an Airflow instance for execution?
Right now the path to the migrations only works if installed locally. This may not be a big issue though, if migrations are deployed the same way DAGs are (they could, I suppose reside just alongside them).