ci(migrate-sboms-to-oci): pin contents: read#10
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
Member
|
thank you! |
The migration job uses OCI_S3_ACCESS_KEY + OCI_S3_SECRET_KEY to push to OCI buckets via the AWS-compatible S3 API. The default GITHUB_TOKEN is only used for the checkout step. Signed-off-by: arpitjain099 <arpitjain099@gmail.com>
arpitjain099
force-pushed
the
ci/add-permissions
branch
from
210f9b8 to
af45f6d
Compare
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
2 participants
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.
Adds a top-level
permissions: contents: readto the SBOM-migration workflow. The actual S3-compatible OCI upload usessecrets.OCI_S3_ACCESS_KEY+OCI_S3_SECRET_KEY, so the defaultGITHUB_TOKENonly needs read access for the checkout.YAML validated locally.