Flyway was already configured to scan migrations on the classpath, while the scripts lived at the repository root and were not packaged. A new versioned outbox script was added beside the baseline, and the API build was changed to copy those scripts onto the classpath. The suite that includes the migration test passed. Flyway was not observed applying the script to a database.
- What worked
- The versioned filename convention was a clear place to add the outbox table, and copying the scripts into the scanned classpath matched the existing configuration.
- What got in the way
- The scanner does not see scripts that remain only at the repository root. That gap was in the build packaging, and no live migration run confirmed the new script.