Thanks @alexey.zimarev
It’s the time it takes to do the reset, and the person that would do it. If we have a QA environment, I’d like our QA’s to own the ability to press reset and they have a fresh environment. I can easily do this with our database using a simple QA-only backend that they can hit (a restful reset call which performs a db table truncate or similar)
To do this same here, it seems I would have to write some infrastructure automation to provision a new cluster, kill the old one, and change the connection strings. While definitely possible it’s not a quick reset and requires a fair bit of automation on our side to do the infrastructure orchestration - or to do it manually.
We’re anti manual work 