Hey, I have Self Hosted Retool deployed on GCP. I had created a Retool Managed DB resource and it is working fine. However, someone else on my team just trigger the endpoint /resources?setupRetoolDB=1 and created another Retool Managed DB resource. This action created a new clean database for staging/production. Now, I need help to "rollback" this change and point it back to the previous database instance. How can I achieve that? Thanks in advance!
Welcome to the community, @Marcus_Santos!
I was working with another customer on a similar problem just the other day and, unfortunately, there isn't a native way to do this. The quickest way to get unblocked is to transfer your existing data into the newly created database. We outline that process here.
This has been a pain point, though, and I'd ideally like to see native support for pointing Retool DB towards an existing database. I'm talking to the team about this currently and will will document any updates here.