Update docker.io/openpolicyagent/opa Docker tag to v0.69.0 #288
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:
0.68.0-debug
->0.69.0-debug
Release Notes
open-policy-agent/opa (docker.io/openpolicyagent/opa)
v0.69.0
Compare Source
This release contains a mix of features, bugfixes and necessary tooling and test changes required to support the upcoming OPA
1.0
release.Inter-Query Value Cache (#6908)
OPA now has a new inter-query value cache added to the SDK. It is intended to be used for values that are expensive to
compute and can be reused across multiple queries. The cache can be leveraged by built-in functions to store values
that otherwise aren't appropriate for the existing inter-query cache; for instance when the entry size isn't an
appropriate or primary limiting factor for cache eviction.
The default size of the inter-query value cache is unbounded, but can be configured via the
caching.inter_query_builtin_value_cache.max_num_entries
configuration field. OPA will drop random items from the cacheif this limit is exceeded.
The cache is used by the
regex
andglob
built-in functions, which previously had individual, non-configurablecaches with a max entry size of
100
each.Currently, the cache is only exercised when running OPA in server mode (ie.
opa run -s
). Also this feature is unsupportedfor WASM.
Authored by @ashutosh-narkar, reported by @amirsalarsafaei
Topdown and Rego
ast
,topdown
,rego
etc. packages to be1.0
compatible (authored by @johanfylling)Module.String()
includeif
/contains
for v1 modules (#6973) authored by @johanfylling reported by @nikpivkinhttp.send
latency timer when an error is encountered (#7007) authored by @lukyerwith
's target (#6979) authored by @srenatus reported by @bluebrownRuntime, Tooling, SDK
sdk
,downlaod
,server
,cmd
etc. packages to be1.0
compatible (authored by @johanfylling)--v0-compatible
flag to make OPA behave asv0.x
postv1.0
release (#7065) authored by @johanfyllingRegoOption
launch option to debugger for setting custom Rego options (#7045) authored by @johanfyllingInput
andData
variable scopes to ease discoverability of the scopes (#7074) authored by @johanfyllingDocs, Website, Ecosystem
1.0
compatible (#7033) authored by @charlieegan3Miscellaneous
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.