wzz6423 opened a new pull request, #66464:
URL: https://github.com/apache/doris/pull/66464

   ## Summary
   
   - Discover numbered AI review auth objects from OSS at runtime.
   - Keep the existing random selection and usage-limit context handling while 
removing the fixed account list.
   
   ## Validation
   
   - Ruby YAML parsing passed.
   - `bash -n` passed for all 21 workflow run blocks.
   - Auth discovery fixture accepted numbered objects and rejected context, 
backup, and status objects.
   - [Production workflow run 
30972681563](https://github.com/wzz6423/doris/actions/runs/30972681563) 
discovered `auth.json.1` through `auth.json.5` and followed their online 
usage-limit contexts.
   - [Isolated auth validation run 
30973370634](https://github.com/wzz6423/doris/actions/runs/30973370634) 
remotely validated all five discovered credentials: four reported no quota and 
one completed successfully.
   
   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: #66119
   
   Problem Summary: The AI review workflow enumerated five OSS credential 
object suffixes, so adding or removing an account required a code change. This 
change lists the `auth.json.` prefix from OSS and retains only numbered 
credential objects before applying the existing shuffle and usage-limit 
handling.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test: Manual test and GitHub Actions
       - YAML parsing, shell syntax validation, filter fixture, production 
workflow, and isolated remote auth validation
   - Behavior changed: Yes (AI review credentials are discovered from OSS 
instead of a fixed account list)
   - Does this need documentation: No
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to