You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a package path overlaps with a rule name (or vice versa), OPA should handle it better.
It seems reasonable to treat this kind of overlap as a conflict and reject at compile-time.
Simple example:
test1.rego...
package x
p = "hello"
test2.rego...
package x.p
q = "goodbye"
queries...
[venv/go](master)[*]torin:~/go/src/github.com/open-policy-agent/opa$ ./opa_darwin_amd64 run ~/test*
OPA 0.1.1-dev (commit b033f78-dirty, built at 2016-11-03T21:24:35Z)
Run 'help' to see a list of commands.
> data.x
{
"p": "hello"
}
> data.x.p
"hello"
> data.x.p.q
"goodbye"
The text was updated successfully, but these errors were encountered:
If a package path overlaps with a rule name (or vice versa), OPA should handle it better.
It seems reasonable to treat this kind of overlap as a conflict and reject at compile-time.
Simple example:
test1.rego...
test2.rego...
queries...
The text was updated successfully, but these errors were encountered: