Fix bug where we revoke cloudsqlsuperuser role from firebasesuperuser #8363
Conversation
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
joehan
approved these changes
Mar 25, 2025
Co-authored-by: joehan <[email protected]>
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.
Last week we added a change to revoke user roles from firebasesuperuser once database setup is complete. This was an issue because if we assign IAM role to firebasesuperuser and we don't revoke it then cloudsql starts treating firebasesuperuser as IAM role and we can't access it anymore.
However, an edge case we didn't consider is cloudsqlsuperuser owning tables/schem, this will basically remove cloudsqlsuperuser access from firebasesuperuser.
Scenarios tested: