fix: postgres provisioning errors when using non-superuser#74
Merged
Conversation
rocketeerbkw
force-pushed
the
fix-postgres-non-superuser
branch
from
f410af1 to
c7aeb5f
Compare
Member
Author
|
Tests failing, showing the bug:
|
Member
Author
|
All tests passing with fix in place. |
shreddedbacon
approved these changes
Apr 15, 2026
Member
There was a problem hiding this comment.
Looks fine to me. I would like to see, and this is probably easier to implement in uselagoon/dbaas-controller#56 though, and that is to set up test cases that covers both types of postgres user.
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
2 participants
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.
Backport of uselagoon/dbaas-controller#56