fix: adding required permissions to top level and jobs in the workflow#7091
Open
gaganhr94 wants to merge 1 commit intooperator-framework:masterfrom
Open
fix: adding required permissions to top level and jobs in the workflow#7091gaganhr94 wants to merge 1 commit intooperator-framework:masterfrom
gaganhr94 wants to merge 1 commit intooperator-framework:masterfrom
Conversation
Signed-off-by: Gagan H R <hrgagan4@gmail.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
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.
Description of the change:
Currently the score for the Token Permissions is 0 because the top level permissions and a few job level permissions are missing in the workflows. With this change, the score will move to 10, since the workflow jobs will run with the minimal permissions. The PR retains conditions like
writeonly at the job level, where it is necessary.Fixes #7090
Motivation for the change:
Improves the OpenSSF Scorecard Token-Permissions check from 0 to 10 by adding minimal top-level permissions (
contents: read) to all GitHub Actions workflows, and keeping anywritepermissions scoped to the specific jobs that need them. This hardens the CI supply chain by following the principle of least privilege forGITHUB_TOKEN.Checklist
If the pull request includes user-facing changes, extra documentation is required:
Add a new changelog fragment inchangelog/fragments(seechangelog/fragments/00-template.yaml)Add or update relevant sections of the docs website inwebsite/content/en/docs