Database migration order blunder caused production error for billing team
Two billing team developers created separate database migrations in the same week, with the second one being deployed first. A previously altered setting in the Flyway migration tool, meant to be temporary, caused the first migration to be silently skipped when it was deployed later. This led to a production error sixteen days later when a customer tried to use the feature dependent on the missing database column. The team has now fixed the tool setting and implemented new safeguards, including timestamp-based versioning and automated checks after deployments.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in