-
Notifications
You must be signed in to change notification settings - Fork 30
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
Saulparedes/fix always allowed #316
base: msft-main
Are you sure you want to change the base?
Conversation
.allow_env_regex_map | ||
.contains_key(&self.name) | ||
{ | ||
panic!( |
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.
Since we are removing the rule that "allows for anything", panic, since the policy we would produce otherwise won't be allowed anyways
@@ -785,11 +785,15 @@ allow_var(p_process, i_process, i_var, s_name, s_namespace) { | |||
|
|||
p_name_value[0] == name_value[0] | |||
|
|||
# TODO: should these be handled in a different way? | |||
always_allowed = ["$(resource-field)", "$(todo-annotation)"] |
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.
if we go with this route, we no longer need resource-field, todo-annotation distinction. These could all be $(validate-from-settings)
] | ||
], | ||
"allow_env_regex_map": { | ||
"JOB_COMPLETION_INDEX": "^[0-9]+$" |
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.
temporarily added for testing. Need to think about how to test our samples without checking in exceptions
Merge Checklist
upstream/missing
label (orupstream/not-needed
) has been set on the PR.Summary
Test Methodology