Skip to content
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

fix: eval variables fixes #104

Conversation

fabriziosestito
Copy link
Contributor

While fixing issue #96, I found that the request object was being passed as a Go struct to the CEL environment. This made its fields only accessible by uppercase names, which isn't what the validating admission policy expects.

Fixes #96 and the request object issue.

@fabriziosestito fabriziosestito added the kind/bug Something isn't working label Dec 4, 2024
@fabriziosestito fabriziosestito self-assigned this Dec 4, 2024
@fabriziosestito fabriziosestito requested a review from a team as a code owner December 4, 2024 12:55
Copy link
Member

@flavio flavio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, can you please tag a patch release to include this fix?

@fabriziosestito fabriziosestito merged commit d28ba6e into kubewarden:main Dec 4, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Policy targeting a sub-resource fails
2 participants