ci: Use DEPENDABOT_AUTH for dependabot-triggered Sonar scans - #119
Merged
Conversation
Dependabot-triggered runs read the Dependabot secret store rather than the Actions one, so `secrets.SECRET_AUTH` resolves to an empty string. The sonar-scanner action then fails to authenticate with Secret Manager and cannot load the github-token secret, surfacing as the misleading `Missing env var: GITHUB_TOKEN`. Select DEPENDABOT_AUTH only when dependabot is the actor, leaving every human-authored run on SECRET_AUTH unchanged. Evidence this is actor-scoped rather than code-scoped: on a single dependabot commit, commit-msg, pre-commit and the ASVS gate all pass and only CI fails -- it is the one workflow that reads the secret. Rebasing or recreating those PRs cannot help, since both preserve dependabot as the triggering actor.
|
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.
Dependabot-triggered runs read the Dependabot secret store rather than the Actions one, so
secrets.SECRET_AUTHresolves to an empty string. The sonar-scanner action then fails to authenticate with Secret Manager and cannot load the github-token secret, surfacing as the misleadingMissing env var: GITHUB_TOKEN.Select DEPENDABOT_AUTH only when dependabot is the actor, leaving every human-authored run on SECRET_AUTH unchanged.
Evidence this is actor-scoped rather than code-scoped: on a single dependabot commit, commit-msg, pre-commit and the ASVS gate all pass and only CI fails -- it is the one workflow that reads the secret. Rebasing or recreating those PRs cannot help, since both preserve dependabot as the triggering actor.