-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
planner: non-string ref keys break #5252
Labels
Comments
srenatus
added a commit
to srenatus/opa
that referenced
this issue
Oct 17, 2022
The compiler ensures that all the keys we see there are scalars. For strings, nothing changes -- they're handled just like before -- but this now also allows numbers and booleans. An example policy that exploded with a panic before is package p a[0] = true when querying the full extent of `data.p` or `data.p.a`. Fixes open-policy-agent#5252. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
srenatus
added a commit
that referenced
this issue
Oct 17, 2022
The compiler ensures that all the keys we see there are scalars. For strings, nothing changes -- they're handled just like before -- but this now also allows numbers and booleans. An example policy that exploded with a panic before is package p a[0] = true when querying the full extent of `data.p` or `data.p.a`. Fixes #5252. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
byronic
pushed a commit
to byronic/opa
that referenced
this issue
Oct 17, 2022
…policy-agent#5257) The compiler ensures that all the keys we see there are scalars. For strings, nothing changes -- they're handled just like before -- but this now also allows numbers and booleans. An example policy that exploded with a panic before is package p a[0] = true when querying the full extent of `data.p` or `data.p.a`. Fixes open-policy-agent#5252. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com> Signed-off-by: Byron Lagrone <byron.lagrone@seqster.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a consequence of #4660.
opa eval
is fine,opa eval -t wasm -d x.rego
isThe text was updated successfully, but these errors were encountered: