Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to protect databases #8

Open
gurjeet opened this issue Jul 11, 2021 · 0 comments
Open

Ability to protect databases #8

gurjeet opened this issue Jul 11, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@gurjeet
Copy link
Contributor

gurjeet commented Jul 11, 2021

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.

@gurjeet gurjeet added the enhancement New feature or request label Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant