-
Notifications
You must be signed in to change notification settings - Fork 10
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
Proposal: Use harden-runner in jobs using OPENTELEMETRYBOT_GITHUB_TOKEN #74
Comments
CC @trask |
the do you mean specifically for the additional fine-grained PATs with write access to a single repo for those who want to grant write permission to @opentelemetrybot? (open-telemetry/community#1503 (comment)) |
Yup. However, it may be safer to use it everywhere where |
@pellared this fell through the cracks. Is it is still actual? |
@tigrannajaryan, yes it is. I think that the proposal should be reviewed by Security SIG. |
cc @open-telemetry/sig-security-maintainers |
@pellared, sounds really cool. Would you be able to make a list of alternatives, and why the one from this specific vendor is the one we should use? We currently have a set of tools provided by the CNCF, like Snyk.io . Couldn't we use one of them instead? |
We can consider using https://github.com/step-security/harden-runner in places where
OPENTELEMETRYBOT_GITHUB_TOKEN
is used.Proposal:
OPENTELEMETRYBOT_GITHUB_TOKEN
so that they add https://github.com/step-security/harden-runnerThe text was updated successfully, but these errors were encountered: