chore(deps): update openpolicyagent/opa docker tag to v1 #17
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.69.0
->1.0.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
open-policy-agent/opa (openpolicyagent/opa)
v1.0.0
Compare Source
We are excited to announce OPA 1.0, a milestone release consolidating an improved developer experience for the future of Policy as Code.
The release makes new functionality designed to simplify policy writing and improve the language's consistency the default.
Changes to Rego in OPA 1.0
Below we highlight some key changes to the defaults in OPA 1.0:
if
for all rule definitions andcontains
for multi-value rules is now mandatory, not just when using therego.v1
import.every
,in
) are available without any imports.opa check --strict
) are now the default. Duplicate imports and imports which shadow each other are no longer allowed.if you must continue to support v0 Rego.
Read more about the OPA 1.0 announcement on the OPA blog.
Following are other changes that are included in OPA 1.0.
Improvements to memory allocations
PRs #7172, #7190,
#7193, #7165,
#7168, #7191 &
#7222 together improve the memory performance of OPA. Key strategies
include reusing pointers and optimizing array and object operations, minimizing intermediate object creation, and using
sync.Pool
to manage memory-heavy operations. These changes cumulatively greatly reduced the number of allocations and improved
evaluation speed by 10-20%. Additional benchmarks highlighted significant memory and speed improvements in custom
function evaluation.
Authored by @anderseknert.
Wrap http.RoundTripper for SDK users
PR #7180 adds an
EvalHTTPRoundTrip
EvalOption and query-levelWithHTTPRoundTrip
option.Both use a new function type which converts an
http.Transport
configured by topdown to anhttp.RoundTripper
.This supports use cases requiring the customization of the
http.send
built in behavior.Authored by @evankanderson.
Improvements to scientific notation parsing in
units.parse
PR #7147 extends the behaviour of
extractNumAndUnit
to supportscientific notation values. This means values such as
1e3KB
can now be handled by this function.Authored by @berdanA.
Support customized buckets
bundle_loading_duration_ns
metricPR #7156 extends OPA’s Prometheus configuration to allow the
setting of user defined buckets for metrics. This aids when debugging the loading of slow bundles.
Authored by @jwu730-1.
Test suite performance improvements
PR #7126 updates tests to improve performance. Topdown and
storage/disk/
tests now run around 50% and 75% faster respectively.
Authored by @philipaconrad.
OPA 1.0 Preparation
rego.v1
andfuture.keywords
imports for v1 by @johanfylling in #7224--rego-v1
cmd flag to--v0-v1
by @johanfylling in #7225Topdown and Rego
topdown/cache
by @evankanderson in #7188to_number
now rejects "Inf", "Infinity" and "NaN" values by @sikehish in #7203Runtime, Tooling, SDK
opa build
: provide an option to preserve print statements for the "wasm" target (#7194) by @me-viper in #7195opa eval
: Return error if illegal arguments passed with--unknowns
flag by @kd-labs in #7149Docs, Website, Ecosystem
Dependency Updates
v0.70.0
Compare 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 bench
by setting the--optimize-store-for-read-speed
flag.More information about this feature can be found here.
Co-authored by @johanfylling and @ashutosh-narkar.
Topdown and Rego
json.match_schema
built-in function (#7011) authored by @anderseknert reported by @lcarvaopa check
where a file that referenced non-provided schemas failed validation (#7124) authored by @tjonsyes
/no
values 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 check
respect--ignore
when--bundle
flag is set (#7136) authored by @anderseknertsuperfluous call to WriteHeader()
while still returning200
HTTP status code. Now, errors encoding the payload properly lead to500
HTTP 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
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 was generated by Mend Renovate. View the repository job log.