vishesh92 opened a new pull request, #13525:
URL: https://github.com/apache/cloudstack/pull/13525

   ### Description
   
   The scheduled agentic workflows ran on a single COPILOT_GITHUB_TOKEN, which 
burns through one person's Copilot quota. Volunteers can now add their own 
fine-grained PATs as COPILOT_GITHUB_TOKEN_<alias> secrets and register the 
alias in the GH_AW_COPILOT_TOKEN_NAMES repo variable. Runs pick a token by day 
of year, skip dead ones, and fall back to the base secret when nothing in the 
pool is live. The two workflows start half the pool apart so they don't drain 
the same volunteer on the same day.
   
   Strict mode forbids reading secrets in the agent job, so each workflow 
defines a pick_copilot_token job that outputs only the chosen alias; the agent 
job resolves the secret itself. gh aw compile doesn't know about this wiring, 
so .github/scripts/post-compile.sh re-applies it to the lock files after every 
compile, including pointing the log redaction step at the rotated token. A 
manual copilot-token-health workflow reports which pool tokens are still live.
   
   See .github/COPILOT_TOKENS.md for how to contribute a token.
   
   
   <!--- Describe your changes in DETAIL - And how has behaviour functionally 
changed. -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   <!--- 
******************************************************************************* 
-->
   <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
******************************************************************************* 
-->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [ ] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ### How Has This Been Tested?
   
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   
   #### How did you try to break this feature and the system with this change?
   
   <!-- see how your change affects other areas of the code, etc. -->
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) 
document -->
   


-- 
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