>This message brought to you by a day of commits dealing with edge cases that only manifest in the cloud environment which uses a "strategic" database technology that is impossible to run locally.
Did you consider running a second test instance of the DB in the cloud?
> Did you consider running a second test instance of the DB in the cloud?
This is using the test instance :) The issue replicates both on prod (cloud) and test (cloud).
But not locally. So a nice 30 minute deployment pipeline run to test if your fix worked, since we are firewalled from direct DB connections from local dev machines, even for test instances.
Did you consider running a second test instance of the DB in the cloud?