Potential fix for code scanning alert no. 1: Workflow does not contain permissions #743
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-application-networking-k8s/security/code-scanning/1
To fix the issue, we will add a
permissions
block at the workflow level to explicitly define the required permissions. Based on the workflow's operations, it likely needscontents: write
to deploy documentation usingmike
. However, we will start with the minimal permissions (contents: read
) and adjust tocontents: write
if necessary for the workflow to function correctly.The
permissions
block will be added at the root level of the workflow, applying to all jobs. This ensures that theGITHUB_TOKEN
used in the workflow has only the necessary permissions.Suggested fixes powered by Copilot Autofix. Review carefully before merging.