You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please add the ability to protect the databases, as well.
Describe the solution you'd like
It should be possible to protect some databases, e.g. supabase_operator_db, so that a customer cannot accidentally drop or modify the databases that are critical to the proper functioning of the Postgres Instance.
Describe alternatives you've considered
None.
Additional context
Since all SQL operations require a database connection, usually the PGaaS provider must connect to some well-defined set (containing at least one DB) of databases. If those databases are dropped, or modified in some way, the health of the DB instance and that of the PGaaS may be at risk.
It may be necessary to even prevent a customer from connecting to these potentially sensitive databases.
The text was updated successfully, but these errors were encountered:
Feature request
Please add the ability to protect the databases, as well.
Describe the solution you'd like
It should be possible to protect some databases, e.g. supabase_operator_db, so that a customer cannot accidentally drop or modify the databases that are critical to the proper functioning of the Postgres Instance.
Describe alternatives you've considered
None.
Additional context
Since all SQL operations require a database connection, usually the PGaaS provider must connect to some well-defined set (containing at least one DB) of databases. If those databases are dropped, or modified in some way, the health of the DB instance and that of the PGaaS may be at risk.
It may be necessary to even prevent a customer from connecting to these potentially sensitive databases.
The text was updated successfully, but these errors were encountered: