I have a golang echo web application and I use atlasgo to do database migrations. From a security best-practice perspective I would like not to bundle my migrations and migration tool into my application container. I need the migrations to run on release though. I.E. I want a different Dockerfile just for the database migrations. Is there a way to have the release_command run from a different image? If not is anyone using a different technique to achieve this?
Effectively what [deploy] release_command does is run fly machine run for you. You can run this command yourself, with a different image, or even a different Dockerfile.