Flyway: Strategy for migrating frequently changing functions / stored procedures

Question

My question is, has anyone found a satisfactory formula for migration large and frequently changing stored procedures?

This question touches on it and has a response from the Flyway author but it's been over a year and a major release with exciting new framework hooks has since been published.

I've added a more thorough description of the problem and my current solution to this flyway github issue but I thought I'd reach out to a wider audience. As described, I have a working solution but has inelegant aspects to it.

I'm wondering if MigrationResolvers or FlywayCallbacks can be put to good use here?

Answer 1

Repeatable Migrations!

Purpose built for this situation, did not exist at time of asking in the 3.x release.