[Infra] Add beam_viewer and beam_writer roles for GSoC 2026 participant#38933
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the project's infrastructure access configuration to provide the necessary permissions for a Google Summer of Code 2026 participant. By explicitly defining the user's roles, the contributor is enabled to perform testing against infrastructure metadata in a controlled environment. Highlights
New Features🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new user, hansmarcus, with viewer and writer permissions to the infra/iam/users.yml configuration. The reviewer noted that the new entry should be moved to its correct alphabetical position to maintain the file's ordering, which helps prevent merge conflicts and improves maintainability.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - username: hansmarcus | ||
| email: hansmarcus14@gmail.com | ||
| member_type: user | ||
| permissions: | ||
| - role: projects/apache-beam-testing/roles/beam_viewer | ||
| - role: projects/apache-beam-testing/roles/beam_writer |
There was a problem hiding this comment.
The users.yml file should maintain alphabetical ordering of users by username to prevent merge conflicts and improve maintainability. Please move this entry to its correct alphabetical position in the file.
|
Assigning reviewers: R: @chamikaramj added as fallback since no labels match configuration Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
2 participants
I am requesting user access (beam_viewer and beam_writer) to the apache-beam-testing project to develop and test the infrastructure monitoring modules for my Google Summer of Code 2026 project.
Project Details
Issue: GSOC-273
Project: Simplify management of Beam infrastructure, access control and permissions via Platform features
Use Case
I am updating the users.yml file to grant my Google account the necessary permissions to interact with GCP APIs during development. These roles will allow me to test my scripts locally against real infrastructure metadata without modifying or destroying production assets.
Request Changes
user.yamlhansmarcushansmarcus14@gmail.combeam_viewer, beam_writer``Mentor
@pabloem