Hi all, I wanted to ask how the community is dealing with post-release steps.

Today we have Ecto migrations, which make sure that the db has been updated to the new schema etc. before the application starts up.

What I’d need is something similar to migrations but for after the application has started. Sometimes after releasing the new code we need to perform some steps like re-publish some events or re-calculate and store some data, and these steps need the newly-released code to be there.

Today we’re taking care of steps like these by connecting to the running app and issuing the necessary commands by hand. Ideally though we’d be able to script these steps in code (and have them be part of pull requests) and then have them run after the app has started successfully, perhaps even schedule them for e.g. after-work hours. And of course if these steps are scripted in code, we’d only run them once (like how ecto migrations are only run once)

Are you aware of something like this existing in the BEAM ecosystem already? If not, how do you deal with such situations? Do you abuse for example Ecto migrations to run non-db related code? Create one-off Oban jobs? Thanks.