Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi team, does anyone can help me understand when these<https://github.com/flyteorg/flyte/blob/e4d29f848efd381bbdf41234b2021fdb94479b75/flyteadmin/pkg/repositories/config/migrations.go#L1104-L1185| two migration ID> will be executed by the command `flyteadmin migrate run`?
If I execute by the path:
1. Upgrade the flyteadmin to v1.14.0, it will <https://github.com/flyteorg/flyte/blob/e4d29f848efd381bbdf41234b2021fdb94479b75/flyteadmin/pkg/repositories/config/migrations.go#L1267-L1274|drop> these two tables.
2. Reverting the flyteadmin to v1.11.0, obviously these two ID are existed, will that be executed and created those two tables back when I ran `flyteadmin migrate run` in v1.11.0 flyteadmin?

<@U06J8TGE6JD>, we use gormigrate to track and run these migrations. Under the covers these migrations are simply rows in a ​`migrations`​ table that gormigrate uses to do its bookkeeping. So, reverting to 1. 11.0 is not enough to re-run the migration. In general it's not advised to revert to older versions unless you have a good reason to. In the specific case of these tables, they were dropped in 1.14 due to a change in how we are handling tags going forward.

I hope this helps. Also, I'd love to understand what problems you're facing with upgrading to 1.14. I know you were seeing an issue with dataclasses, but was there any other issue? Thanks.
