-
Notifications
You must be signed in to change notification settings - Fork 60.5k
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
Documentation about secrets for step condition could elaborate on implications of the approach #18955
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
@m-kuhn Thanks for opening a new issue for this. I'll get it triaged for review! ⚡ |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
This comment was marked as spam.
This comment was marked as spam.
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
This is a gentle bump for the docs team that this issue is waiting for technical review. |
I think this would deserve a hint on the implication that the secret is leaked to every step within the job, regardless if it's required for a certain step or not (hence violating the principle of least privilege).
Originally posted by @m-kuhn in #12722 (comment)
The text was updated successfully, but these errors were encountered: