fix(deps): update module github.com/open-policy-agent/opa to v1.9.0 #4842
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.8.0
->v1.9.0
Release Notes
open-policy-agent/opa (github.com/open-policy-agent/opa)
v1.9.0
Compare Source
This release contains a mix of new features, performance improvements, and bugfixes. Notably:
Compile Rego Queries Into SQL Filters (#7887)
Compile API extensions with support for SQL filter generation previously exclusive to EOPA has been ported into OPA.
Example
With OPA running with this policy, we'll compile the query
data.filters.include
into SQL filters:Example Request
Example Response
See the documentation for more details.
Authored by @srenatus and @philipaconrad
Improved Rule Indexing For "Naked" Refs (#7897)
OPA's rule indexer is a means by which OPA can optimize evaluation performance.
Briefly, the indexer can in some cases determine that a rule won't successfully evaluate before it's evaluated based on the query input.
The indexer previously only considered terms in certain compound expressions, ignoring single terms; e.g. an expression containing a sole "naked" ref. This has now changed!
Example
Given a policy with an
allow
rule containing two "naked" refs:input.foo
andinput.bar
:and the input document:
before this improvement, when evaluating the query
data.example.allow
, we get the trace log:Here, we can see that the
allow
rule is evaluated, but fails on theinput.bar
expression, as it's referencing anundefined
value.With the improvement to the indexer, we instead get:
Where we can see that the
allow
rule was never evaluated, since the input doesn't meet the conditions established by the indexer; i.e. bothinput.foo
andinput.bar
must havedefined
values.Authored by @srenatus
Runtime, Tooling
opa run
when loading bundles in watch-mode (--watch
) (#7870) authored by @sspaink reported by @johanfyllingCompiler, Topdown and Rego
numbers.range_step
built-in error message (#7882) authored by @charlieegan3Docs, Website
every
andnot
examples (#7901) authored by @charlieegan3io.jwt
andtime
built-ins (#7892) authored by @charlieegan3regex
andstring
built-ins (#7890) authored by @charlieegan3Miscellaneous
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.