potiuk commented on pull request #19637: URL: https://github.com/apache/airflow/pull/19637#issuecomment-971902648
> I would still suggest of a separate CLI command like #19471 or run `airflow db upgrade` with a flag (`--with-reserialize-migrations` or similar) to have a switch in case things go wrong. One thing that I really do not like here is that it forces the admin users to "know" about the serialization, be able to diagnose problems connected with it and map it mentally to the switch or command line. This should be totally transparent to them - this is an implementation detail of airflow which is important to us but it should be totally invisible to the users. I can't even imagine a good "admin description" on WHEN the user should use such a flag? What is the criteria they should be using to decide when to use it? -- 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]
