Ephemeral Databases for Every PR: Using the Filess Shared API in CI/CD
You've built a feature. It works on your machine. You open a PR.
Your CI pipeline runs unit tests. They pass. Your reviewer approves the PR.
You merge. You deploy. Production breaks.
The bug was a subtle interaction between your code and the database schema — something unit tests couldn't catch because they mock the database. Integration tests could have caught it, but your integration test suite either doesn't exist or runs against a shared staging database that's full of dirty state from the last developer who also tested there.
The real fix is an ephemeral database per PR: a fresh database, identical to production schema, provisioned when the PR opens and destroyed when it merges. Your integration tests run against it. Nothing shares state between PRs.
Filess has two APIs. Knowing which one to use matters.