-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add content write permissions to release jobs #1555
Add content write permissions to release jobs #1555
Conversation
This issue is currently awaiting triage. If metrics-server contributors determine this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth explicitly setting the default workflow level permissions for the other 2 workflows in this PR?
196e9f0
to
b3a86bf
Compare
@stevehipwell I udpated the PR, is this what you had in mind? I removed the top-level permissions entirely as these are inherited from the repo settings which sets everything to read-all. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dgrisonnet setting the top level permissions is a best practice as it stops accidental (or deliberate) permission creep. Tools such as the OSSF Scorecard will warn if this isn't set.
FYI I can recommend using https://app.stepsecurity.io/secureworkflow with the agent option unchecked to check GH workflows are secure, this is what the OSSF Scorecard recommends using too.
Oh I see, that makes sense. Thanks for the tip, I'll run the workflow through that tool |
b3a86bf
to
dde9422
Compare
@dgrisonnet I still think it'd be worth adding the default to the other workflows while you're doing these ones. |
@dgrisonnet are you still working on this? |
Signed-off-by: Damien Grisonnet <[email protected]>
dde9422
to
60694b9
Compare
Yes sorry about that, I missed your last comment |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test pull-metrics-server-verify
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgrisonnet, yangjunmyfm192085 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This should work around the org-wide restriction on github actions write permission to the repos and fix the issue I encountered when releasing v0.7.2 where the jobs to publish the assets failed: https://github.com/kubernetes-sigs/metrics-server/actions/runs/10593979544