Fix Database ordering and execution
Problem to solve
We need to guarantee that what we test on staging goes out to production. Ideally it should be anchored to a SHA (ordering, migrations, code, everything). We should also protect the application from ungracefully failing when ordering is not correct or enforced.
Our Database schema is tightly coupled with Rails and when it sees it, it assumes that's the way it's going to be. Production is running and more dynamic. This coupling will cause us operational issues.
Solutions we have considered, but won't do and reasons
Intended users
Further details
Proposal
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Christopher Lefelhocz