Add module for using cloud identity api to manage google groups#5149
Merged
ViniciustCosta merged 8 commits intomasterfrom Feb 2, 2026
Merged
Add module for using cloud identity api to manage google groups#5149ViniciustCosta merged 8 commits intomasterfrom
ViniciustCosta merged 8 commits intomasterfrom
Conversation
ViniciustCosta
changed the title
ViniciustCosta
changed the title
ViniciustCosta
requested review from
decoNR,
hunsche,
javanlacerda and
vitaliset
vitaliset
approved these changes
Feb 2, 2026
decoNR
approved these changes
Feb 2, 2026
javanlacerda
reviewed
Feb 2, 2026
Collaborator
javanlacerda
left a comment
javanlacerda
left a comment
There was a problem hiding this comment.
Is there a way to test it in dev ?
Collaborator
Author
Not actually as this will only be used by OSS-Fuzz (and dev simulates chrome environment). The plan here is to create a separate cronjob (already did in #5151) to create and sync the OSS-Fuzz projects' groups initially. Afterwards, I will adapt the issue tracker to CC the groups instead of the actual emails. Once everything is working fine, then we can integrate the group syncing step into the project-setup cron. |
javanlacerda
pushed a commit
that referenced
this pull request
Feb 4, 2026
This is some groundwork in order to use google groups for CCs in OSS-Fuzz issues. Context: b/477964128, b/388390041 and google/oss-fuzz#12945 Since we used google groups for the auth/access in appengine, I updated it to centralize in the same module under google cloud utils. Tests: * Used a local script (gpaste/4919004936404992) to execute all methods using a test group. Output: gpaste/6567249169219584
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
4 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.
This is some groundwork in order to use google groups for CCs in OSS-Fuzz issues.
Context: b/477964128, b/388390041 and google/oss-fuzz#12945
Since we used google groups for the auth/access in appengine, I updated it to centralize in the same module under google cloud utils.
Tests: