Potential fix for code scanning alert no. 2: Workflow does not contain permissions #438
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.
Potential fix for https://github.com/aws/aws-xray-sdk-java/security/code-scanning/2
To fix the problem, you should add a
permissionsblock to the workflow file. The preferred location is at the root level (top of the YAML), which will apply these permissions to all jobs that don't specify otherwise. The minimal, most secure starting point iscontents: read, because all shown steps require at most read access to repository contents for checking out code, reading dependencies, caching, reporting, and publishing with secrets provided, rather than relying onGITHUB_TOKENwrite access. No steps require write access to the repository viaGITHUB_TOKEN(such as pushing code, creating PRs, or drafting releases). This change is made by inserting thepermissionsblock immediately following thename:key (after line 1) in.github/workflows/master-build.yml.Needed steps:
name: Master Buildline (line 1).contents: read.Suggested fixes powered by Copilot Autofix. Review carefully before merging.