-
Notifications
You must be signed in to change notification settings - Fork 252
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
Ensure that per-service postgres users are not superusers #2498
Comments
This is because when users are created with gcp's command line tooling, they automatically get the I have verified that the credentials with which |
If this can be done in such a way that
then it sounds okay. What will happen by default if we continue setting up the non-admin users the way edunham is doing it is
We can verify by testing after this command is run and seeing
|
So far we've been checking but not enforcing permissions in db:upgrade. The idea is that any discrepancy is potentially an IOC and we don't want to sweep it under the rug. So I'll continue to do that here. |
|
|
In
db:ugprade
, we check that per-table permissions correspond to those indb/access.yml
, but we don't look at whether a user is a superuser. We should.The text was updated successfully, but these errors were encountered: