Allow the exact Global ETF job workflow identity - #241
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The auth-only run 35135230905 identified service HTTP 401 with job_workflow_ref_not_allowed. GitHub supplies this second identity claim for the Global ETF workflow; its workflow_ref was already permitted, but the job allowlist omitted it.
Add only the exact Global ETF main job-workflow identity to both deployment sources. Keep all other entries and the first allowlist unchanged. Regression tests exercise the actual two-claim payload and reject other branches and job workflows.
Validation: 29 focused tests passed, 1 skipped, 19 subtests; actionlint, Ruff, Bash syntax and diff checks passed. No research/model execution or trading changes.