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

Strict-mode shouldn't allow rule ref-heads to shadow input and data documents #6291

Closed
johanfylling opened this issue Oct 10, 2023 · 2 comments · Fixed by #6417
Closed

Strict-mode shouldn't allow rule ref-heads to shadow input and data documents #6291

johanfylling opened this issue Oct 10, 2023 · 2 comments · Fixed by #6417
Assignees

Comments

@johanfylling
Copy link
Contributor

Currently, when strict-mode is enabled, rules like data.a.b := 1 and input.a.b := 1 doesn't generate errors.

Today, the input case will cause a complete replacement of the input document.

The data case doesn't produce error or output (!).

@ashutosh-narkar
Copy link
Member

@johanfylling it would be good if we can enforce this check as part of the future.strict import. Even if we get #6285 in first, future.strict can enforce this later, correct?

@johanfylling
Copy link
Contributor Author

Yes, I think we shouldn't be afraid of adding new checks/stuff to future.strictfuture.compat even after it's live.

Some other things that we should gate behind the future.compat import, if we have the opportunity:

There is probably some point in time leading up to the 1.0 release where we should stop adding content; which we also need to communicate.

johanfylling added a commit to johanfylling/opa that referenced this issue Nov 16, 2023
when:
* strict-mode is enabled
* `rego.v1` is imported

Fixes: open-policy-agent#6291
Signed-off-by: Johan Fylling <[email protected]>
ashutosh-narkar pushed a commit that referenced this issue Nov 16, 2023
when:
* strict-mode is enabled
* `rego.v1` is imported

Fixes: #6291
Signed-off-by: Johan Fylling <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

2 participants