Skip to content

ci(migrate-sboms-to-oci): pin contents: read - #10

Merged
mfahlandt merged 1 commit into
cncf:mainfrom
arpitjain099:ci/add-permissions
Jun 2, 2026
Merged

ci(migrate-sboms-to-oci): pin contents: read#10
mfahlandt merged 1 commit into
cncf:mainfrom
arpitjain099:ci/add-permissions

Conversation

@arpitjain099

Copy link
Copy Markdown
Contributor

Adds a top-level permissions: contents: read to the SBOM-migration workflow. The actual S3-compatible OCI upload uses secrets.OCI_S3_ACCESS_KEY + OCI_S3_SECRET_KEY, so the default GITHUB_TOKEN only needs read access for the checkout.

YAML validated locally.

@mfahlandt

Copy link
Copy Markdown
Member

thank you!
Altough the script is obsolete, it would be good to have this in for documentation prupose.
Can you Sign your commit, then i will merge it
https://github.com/cncf/sbom/pull/10/checks?check_run_id=75776005493

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>
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
@arpitjain099

arpitjain099 commented Jun 2, 2026

Copy link
Copy Markdown
Contributor Author

thank you! Altough the script is obsolete, it would be good to have this in for documentation prupose. Can you Sign your commit, then i will merge it https://github.com/cncf/sbom/pull/10/checks?check_run_id=75776005493

@mfahlandt done, please check the PR again

@arpitjain099

Copy link
Copy Markdown
Contributor Author

Hi @mfahlandt, the commit is signed now: it shows as Verified and the DCO check is green. Ready to merge whenever you have a moment. Thanks!

@mfahlandt
mfahlandt merged commit cf0c18a into cncf:main Jun 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants