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

Update OPA to version 0.58.0 #79

Merged
merged 1 commit into from
Nov 20, 2023

Conversation

larhauga
Copy link
Contributor

This pull requests updates go.mod for OPA version v0.58.0.
It also updates the vendored catalog to support the dependency changes.

The intent is to update OPA to a version that includes the future package with the "in" keyword.

Thanks!

go get -u github.com/open-policy-agent/[email protected] && go mod tidy
update vendor: go mod vendor

Signed-off-by: Lars Haugan <[email protected]>
@anderseknert anderseknert merged commit 98ac3f4 into open-policy-agent:main Nov 20, 2023
4 checks passed
@anderseknert
Copy link
Member

Thanks Lars! The in keyword has been in OPA since v0.34.0 or something like that, so it should already have worked. Did you find it didn't?

@larhauga
Copy link
Contributor Author

larhauga commented Nov 20, 2023

Hi @anderseknert and thanks for your quick reply!
I found it working locally with "opa test" directly, but through the plugin i got some issues.

I have tested with the openpolicyagent/opa-docker-authz-v2:0.8 image from dockerhub, which I now can see is two years old :)
Could it be that this needs to be updated as well?

2023-11-20T06:49:21Z" level=error msg="2023/11/20 06:49:21 Returning OPA policy decision: false (error: 1 error occurred: 1 error occurred: /opa/opa-conf.rego:3: rego_parse_error: unexpected import path, must begin with one of: {data, input}, got: future
2023-11-20T06:49:21Z" level=error msg="\timport future.keywords.in

The start of the policyfile (/opa/opa-conf.rego) is:

package docker.authz

import future.keywords.in

allow {
...

@anderseknert
Copy link
Member

Yeah, not a whole lot have been going on here for some time, so your fixes are more than welcome. I'll take a look at your other PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants