-
Notifications
You must be signed in to change notification settings - Fork 41
feat(policy): implement policy eval #2611
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
Conversation
migmartri
left a comment
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.
See inline comments, I am not sure why we need to move the evaluation server-side for this change cc/ @jiparis
Yes, this PR before was only about remote execution, the idea was to use server side execution as part of declarative control gates (which we decided to not implement). But remote execution was moved out of scope for this project so I cleaned up the PR. Now it contains only changes related to the new command. Sorry about that. |
Signed-off-by: Sylwester Piskozub <[email protected]>
Signed-off-by: Sylwester Piskozub <[email protected]>
Signed-off-by: Sylwester Piskozub <[email protected]>
Signed-off-by: Sylwester Piskozub <[email protected]>
Signed-off-by: Sylwester Piskozub <[email protected]>
Signed-off-by: Sylwester Piskozub <[email protected]>
Signed-off-by: Sylwester Piskozub <[email protected]>
Summary
Introduces a new
chainloop policy evalcommand that evaluates policies using the control plane with organization settings, supporting both generic and material-based policy evaluation.Differences
--allowed-hostnames