fix(dd-octo-sts): pin org/repo IDs in publish policy subject_pattern - #46
Merged
Conversation
The ddoghq org includes numeric org/repo IDs in the OIDC sub claim (repo:ddoghq@230443989/datadog-client-plugin@1348581382:ref:...) rather than plain names, which breaks the release trust policy's subject_pattern (see ddoghq/datadog-client-plugin#277). Applies the same fix here since this file mirrors that repo's public-repo-files policy. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.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.
Summary
ddoghqorg includes numeric org/repo IDs in the OIDCsubclaim (repo:ddoghq@230443989/datadog-client-plugin@1348581382:ref:...) rather than plain names, which breaks the trust policy'ssubject_pattern— see ddoghq/datadog-client-plugin#277.datadog-client-plugin'spublic-repo-files/.../datadog-client-plugin.publish.sts.yaml, so it hits the same mismatch. Applies the identical fix here.Test plan
mainand confirm the nextv*-publicrelease tag'sdd-octo-ststoken exchange succeeds🤖 Generated with Claude Code