Direct DB access has been replaced by an intermediate service, and a new service is needed to run the DAG processor. We should be able to apply these changes in place, but the infra changes are significant enough to require some extra testing in a low-stakes environment.

Ref: https://airflow.apache.org/docs/apache-airflow/stable/installation/upgrading_to_airflow3.html#understanding-airflow-3-x-architecture-changes

At first read, this looks like DB connections have been refactored and a new service has been added to facilitate worker -> DB connections. These changes will need to be applied at the module level for SM2A, and possibly in the Dockerfiles for each core service as well.

AC

• Airflow 3.0+ is deployable using https://github.com/NASA-IMPACT/self-managed-apache-airflow/ - marked as a major version upgrade, since these are breaking changes.