Hi,
We would like to modify the access to the public schema that occurs during the migration executed when running a self-hosted Retool container, so that it uses a different schema instead. Is there a way to do this?
For the security certification our company is preparing for, compliance requires that access to the public schema in PostgreSQL be prohibited. However, it seems that access to the public schema is being enforced in the migration code during the current Retool migration process.
We would be grateful if you could provide us with a solution.
Our Retool environment is as follows:
- k8s
- self hosted retool 3.39.0 (enterprise)
And here is a screenshot that we believe shows Retool enforcing the use of the public schema.
