We've started an internal discussion if we need to implement a different or better interface for this kind of configuration in flyway.
For the moment, the most scalable path of least resistance in our estimation is scripting the change as opposed to recomposing, and then inserting that via a Docker entry point.
This does admittedly have a slightly higher initial setup cost if the user isn't familiar with scripting environmental alterations.
Using your example, writing the certs to the keystore in a bash script called entrypoint.sh and then including it in the initial flyway invocation.
docker run -v ".\entrypoint.sh:/flyway/entrypoint.sh" "--entrypoint=/flyway/entrypoint.sh" redgate/flyway
Sean Quigley | Product Support Engineer | Redgate Software
Have you visited our Help Center?
Tips and how-to guides for Redgate products
Ask, discuss, and solve questions about Redgate's tools
Meet us at an event, get sponsored, and join our Friends of Redgate
In-depth articles and opinion from Redgate's technical journal