Adaverse commented on issue #32048: URL: https://github.com/apache/airflow/issues/32048#issuecomment-1626321204
Currently, `airflow db init` does two main tasks - a. This command init the database if it dosen't exist, upgrade it if exist, load the default pools and synchronizes log_filename_template with the db b. Create default connections We all agree to remove the (b) part of the `db init` and move it to `db create-airflow-connections`. Also, there are some suggestions to remove `db init` entirely in favor of `db upgrade` + `db create-airflow-connections` IMO it is best to leave `db upgrade` as it is. Just remove the (b) part of `db init` to the `db create-airflow-connections` and leave the (a) part in `db init` untouched. The reason not to touch `db upgrade` is that it does exactly what its name suggests. The reason for keeping `db init` with only (a) part is that it comes closer to what its name suggests. Also, changing things this way brings minimum changes from user perspective i.e just add `db create-airflow-connections` in the flow if default connections are needed and keep everything the way it is. Let me know what you guys think so that we can proceed with #32420 -- 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]
