Update openpolicyagent/opa Docker tag to v0.70.0 #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chris-sanders
force-pushed
the
renovate/openpolicyagent-opa-0.x
branch
from
1fb1b86
to
97aed7d
Compare
chris-sanders
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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->0.70.0Release Notes
open-policy-agent/opa (openpolicyagent/opa)
v0.70.0Compare Source
This release contains a mix of features, performance improvements, and bugfixes.
Optimized read mode for OPA's in-memory store (#7125)
A new optimized read mode has been added to the default in-memory store, where data written to the store is eagerly converted
to AST values (the data format used during evaluation). This removes the time spent converting raw data values to AST
during policy evaluation, thereby improving performance.
The memory footprint of the store will increase, as processed AST values generally take up more space in memory than the
corresponding raw data values, but overall memory usage of OPA might remain more stable over time, as pre-converted data
is shared across evaluations and isn't recomputed for each evaluation, which can cause spikes in memory usage.
This mode can be enabled for
opa run,opa eval, andopa benchby setting the--optimize-store-for-read-speedflag.More information about this feature can be found here.
Co-authored by @johanfylling and @ashutosh-narkar.
Topdown and Rego
json.match_schemabuilt-in function (#7011) authored by @anderseknert reported by @lcarvaopa checkwhere a file that referenced non-provided schemas failed validation (#7124) authored by @tjonsyes/novalues as boolean. The usage of yaml.v2 in the parser was unintentional and now has been updated to yaml.v3 (#7090) authored by @anderseknertRuntime, Tooling, SDK
opa checkrespect--ignorewhen--bundleflag is set (#7136) authored by @anderseknertsuperfluous call to WriteHeader()while still returning200HTTP status code. Now, errors encoding the payload properly lead to500HTTP status code, without extra logs. Also use Header().Set() not Header().Add() to avoid duplicate content-type headers (#7114) authored by @srenatusfile://format for TLS key material file flags inopa run(#7094) authored by @alexrohozneanuDocs, Website, Ecosystem
Miscellaneous
v0.69.0Compare Source
This release contains a mix of features, bugfixes and necessary tooling and test changes required to support the upcoming OPA
1.0release.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_entriesconfiguration field. OPA will drop random items from the cacheif this limit is exceeded.
The cache is used by the
regexandglobbuilt-in functions, which previously had individual, non-configurablecaches with a max entry size of
100each.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,regoetc. packages to be1.0compatible (authored by @johanfylling)Module.String()includeif/containsfor v1 modules (#6973) authored by @johanfylling reported by @nikpivkinhttp.sendlatency timer when an error is encountered (#7007) authored by @lukyerwith's target (#6979) authored by @srenatus reported by @bluebrownRuntime, Tooling, SDK
sdk,downlaod,server,cmdetc. packages to be1.0compatible (authored by @johanfylling)--v0-compatibleflag to make OPA behave asv0.xpostv1.0release (#7065) authored by @johanfyllingRegoOptionlaunch option to debugger for setting custom Rego options (#7045) authored by @johanfyllingInputandDatavariable scopes to ease discoverability of the scopes (#7074) authored by @johanfyllingDocs, Website, Ecosystem
1.0compatible (#7033) authored by @charlieegan3Miscellaneous
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.