potiuk commented on issue #32048: URL: https://github.com/apache/airflow/issues/32048#issuecomment-1600733529
I am not sure if this is really needed. As discussed in https://github.com/apache/airflow/pull/31533#discussion_r1236891857 "airflow db init" is mostly a "try and test" feature. There are a a number of things that we should be aware of: * It is discouraged to be used in production: https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/production-deployment.html#database-backend: > Do not use airflow db init as it can create a lot of default connections, charts, etc. which are not required in production DB. So the objective of the `airflow db init` command is different than what is suggested here. In the ideal world people will not have those connections created in production and we had absolutely no intention to synchronize those connections with anything. There are a number of problems and considerations to solve if we want to do any kind of any attempt of production-level synchronization. All of them are described and extensively discussed here: https://github.com/apache/airflow/issues/31875 I think the root cause of the problem is the `airflow db init` name, that suggest that it should be use as first thing when you set-up the database, where it is only intended to be use if you want to "play" with airflow when you first try it. IMHO we should continue the path that the `airflow db init` is not production ready, and no synchronisation intended feature. I would rather deprecate the `airflow db init` and rename it to `create-default-connections` or similar. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
