Migration-safe releases on Azure Container Apps

The scariest part of deploying a payment platform is the database migration: get it half-applied and you've got an outage mid on-sale. We rebuilt Rebll's release so that can't happen. Each deploy packages its database changes into a self-contained migration bundle, and — behind a manual approval gate — runs it against Azure SQL, rolls the new container image, and then checks the health endpoint to confirm the app came back up.

If anything fails, the release stops rather than limping on. Combined with the whole environment being defined in Bicep and secrets pulled from Key Vault at startup, deploys have gone from a held-breath event to something routine.