HansMarcus01 opened a new pull request, #38819:
URL: https://github.com/apache/beam/pull/38819

   **Please** add a meaningful description for your change here
   
   I am requesting a service account key for my Google Summer of Code 2026 
project.
   
   ### Project Details
   **Issue:** [GSOC-273](https://issues.apache.org/jira/browse/GSOC-273)
   **Project:** Simplify management of Beam infrastructure, access control and 
permissions via Platform features
   
   ### Use Case
   This service account will be used to implement the **key lifecycle and 
compliance monitoring system**, which includes:
   
   1. **Operational Monitoring of Service Keys and Compliance**
      - Continuous inventory and labeling of service accounts and keys
      - Automated tracking of key creation dates, responsible parties, and TTL
      - Verification of key rotation and Secret Manager propagation
      - Usage and compliance monitoring via GCP Audit Logs and BigQuery
   
   2. **Supporting Infrastructure Components**
      - BigQuery dataset (`beam-security.key_lifecycle`) for metrics and audit 
trails
      - GitHub Actions workflows for automated compliance checks
      - Cloud Monitoring dashboards for infrastructure health visualization
   
   ### Requested Service Account
   - **Account ID:** `hansel-gsoc-2026`
   - **Authorized User Email:** `[email protected]`
   
   ### Mentor
   [@pabloem](https://github.com/pabloem)
   
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable. This will automatically add a link to the 
pull request in the issue. If you would like the issue to automatically close 
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/actions/workflows/build_wheels.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/actions/workflows/python_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/actions/workflows/java_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/actions/workflows/go_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI or the [workflows 
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) 
to see a list of phrases to trigger workflows.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to