)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"f0c1feb13547b5dee5a2555073ddbb6439d21723","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"818a664b_30f5db89","updated":"2022-09-06 07:19:09.000000000","message":"This is a sensible thing to do. You missed some pieces though, like \u0027oslo_db/sqlalchemy/migration_cli/manager.py\u0027","commit_id":"f1800221399325d20190cc2c4017ae27c947f8c1"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"55d16dd86c9ce2b2c6a547d22b353423ea407e46","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"cb8d1355_77be2f92","updated":"2023-02-27 12:14:42.000000000","message":"I guess we can merge this now that we\u0027ve branched?","commit_id":"d82e30cfa132607636755f5f12f7e04f77560f2b"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"f5e5efeeb3b0640ceeaba32507d9b0bafb1cfd2f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"6cc6073c_927ac99d","updated":"2023-02-27 15:07:02.000000000","message":"I\u0027ve modified this to avoid removing the \u0027migration_cli\u0027 module entirely. There\u0027s no need for us to be so aggressive. Simply removing the \u0027migrate\u0027 backend should be sufficient for now.","commit_id":"d82e30cfa132607636755f5f12f7e04f77560f2b"},{"author":{"_account_id":11816,"name":"mike_mp@zzzcomputing.com","display_name":"Mike Bayer","email":"mike_mp@zzzcomputing.com","username":"zzzeek","status":"Red Hat"},"change_message_id":"3db3088e53471400524bd1d4617f67eb0b1ef024","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"c81c4d86_6e174f1c","updated":"2023-02-27 13:12:21.000000000","message":"im sure I\u0027ve asked this a lot and have just forgotten the answer.   do we know what major openstack components are still using migrate these days?","commit_id":"d82e30cfa132607636755f5f12f7e04f77560f2b"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"c891b63058ff1ba9d5d260738662924778c62497","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"73d6eb5a_031156fb","in_reply_to":"c81c4d86_6e174f1c","updated":"2023-02-27 14:56:44.000000000","message":"nova, keystone and cinder all have legacy migrate-based migrations but have been using alembic for new migrations for a number of releases. I\u0027ve proposed patches for nova [1] and cinder [2] to drop these legacy migrations, which I hope to merge early in B. I still need to do the keystone one.\n\nheat, masakari, freezer-api, trove, ec2-api, senlin, and venus are using migrate-based migrations [3] but do not appear to have been using alembic. I\u0027m not sure how many of these are still alive, and I certainly won\u0027t be able to migrate them. Those projects will need to vendor this code themselves and work to get off migrate/modify it to work with SQLAlchemy 2.0.\n\n[1] https://review.opendev.org/c/openstack/nova/+/872428\n[2] https://review.opendev.org/c/openstack/cinder/+/874241\n[3] https://codesearch.opendev.org/?q\u003doslo_db.sqlalchemy%20import%20migration\u0026i\u003dnope\u0026literal\u003dnope\u0026files\u003d\u0026excludeFiles\u003d\u0026repos\u003d","commit_id":"d82e30cfa132607636755f5f12f7e04f77560f2b"}]}