Fix postgres non superuser#56
Merged
Merged
Conversation
Member
Author
|
Ran tests at commit |
Member
Author
|
Tests passing with the fix in place https://github.com/uselagoon/dbaas-controller/actions/runs/24212383544/job/70684296367?pr=56. |
Member
Author
|
Added test case for postgres superuser, as suggested in amazeeio/dbaas-operator#74 (review) |
shreddedbacon
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When
dbaas-controllermanages a postgres database using a non-superuser, it's not able to provision or delete databases.Errors provisioning:
Errors deleting:
In order to continue letting provisioned users own the provisioned database, the fix is to grant access to the provisioned user for the
dbaas-controlleruser. That way, it has permission to set owner and delete the database it's not directly an owner of.Follow up to #34