The actions-oidc-gateway-example from github

[Fanout Tracking] package-security - Proxima Services Fully Functional in the Australia Stamp

Fanout Effort

https://github.com/github/fanout/issues/1541

🚦 Status

Field	Value
Trending	⚪ inactive
Company Priority	Priority 1

🧳 Accountability

Field	Value
Exec Sponsor	nerdneha
DRI	@trevrosen
Product Area

📅 Key Dates

Field	Value
Start Date	2024-05-15
Target Date	2024-06-30
Last Report Date

🏔 Fanout Summary

In Q3FY24 we have successfully onboarded our external Alpha customers in the EU stamp. In Q4FY24 , we are expanding beyond EU and turning our attention to our regional roll out starting with the Australia stamp. In order to do this, we are asking all the teams to be fully functional in the Australia Stamp, prioritize automation, and record the time to stand up infrastructure and become fully functional.

📈 Overview of the Requested Work

We are expecting at least 4 additional stamps in FY25 and more in FY26. Therefore, as part of building out the AUS stamp this quarter, teams should plan and investigate automation to make future stamp creation faster so that we can achieve these goals. This is the first time both infrastructure and services are getting onboarded during the same quarter. As such teams should be aware of the timing. Infrastructure will be deployed during the first month of the quarter and service teams will be able to start onboarding from May 15, 2024 or sooner. We will communicate the changes in the Fanout issue when the Australia stamp infrastructure is ready for service onboarding. Until then, the Fanout issue status stays inactive.

Important

Teams should plan and implement opportunistic high-ROI automation this quarter. The planning work for this can start before infrastructure is ready on May 15th, 2024 (or sooner).
As part of this Fanout, we request teams should document the duration and developer resources required to 1) stand up any additional infrastructure your team uses and 2) achieve full functionality in AUS including end to end testing. Please include this information in this spreadsheet before marking this issue as closed.
We are expecting at least 4 additional stamps in FY25 and more in FY26. Please document particular areas where automation can streamline future onboarding for your team, along with an estimated effort for implementing such automation and the anticipated time savings before closing this issue. Alternatively, if the automation is feasible within the quarter, consider building the automation first and then using it to spin up this stamp.

🚦 Success Target

The DRI will provide weekly updates by Wednesday 5 PM PT for each of the Fanout issues.
Updates are submitted in this Fanout issue by calling the /short-report issue comment template.

📝 Supporting Materials

Fully Functional Service Guidance
New Stamp creation playbook
Heaven Pipelines Onboarding
Proxima Observability Guidance
For support, there are various #proxima-* channels depending on what is needed.
For help with deployments or pipeline updates come by #deploy-support.
For observability help use #observability.
For tenancy questions stop by #proxima-tenancy.

✔️ Tasklist

Tasks

Beta Give feedback

Your service is onboarded to pipelines and continuously deploying to Staffship, Dotcom, EU Stamp and the Australia stamp. It blocks on deployment failures to any stamp.
Your service is working as expected in Proxima and does not expose tenant suffixes in UI and API customer facing experiences
Your service has completed a bug bash on the Proxima Australia Stamp, and you’re ready to accept bug reports and resolve bugs per SLOs.
Your service has metrics, dashboards, and alerting in place for the Proxima Australia Stamp
Any low effort high ROI automation is implemented
You have updated this spreadsheet with the estimated effort and time savings of implementing automation for your area (if not implemented this quarter).
Options

actions-oidc-gateway-example repo access for the newly named Frameworks and Containers team

The Frameworks for Services team has been renamed Frameworks and Containers. See https://github.com/github/engineering/discussions/2454.

The existing https://github.com/orgs/github/teams/frameworks-services team has write permissions to the actions-oidc-gateway-example repo, and we'd like to request the same write permissions for the new https://github.com/orgs/github/teams/frameworks-containers team so that when we archive the old team we won't lose access to any repos.

github / actions-oidc-gateway-example Goto Github PK

actions-oidc-gateway-example's People

Contributors

Stargazers

Watchers

Forkers

actions-oidc-gateway-example's Issues