not sure how. But when I asked GPT with this line and the issue was found exactly.
The issue is tiny and slipery for a very big table. But I am still curious of
why test can not find it.
>During the work day, this was fine. We probably committed 10-20 times a day (directly to main of course) which would cause new backend deployments to occur, giving us 40 new IDs for customers to potentially use.
They just use the test env for prod?
When to push code, the CICD should be run and some examples should be run too here. And every time, the env should be clean.
Here the database does not change from test to production.
I came accross a lot of such info from redhat. And I tried podman which is not bad because my scenario was not complicated. But days before, I tried podman-compose which behaved so poor. That's a pitty. After years, podman's ecosystem is so poor. I don't want to be trapped by sorts of small/hidden pitfalls. I have to switch back docker then. The quality prevails, not the advertisement. PS: I did not read the passage. The title is enough.