Path to this page:
Subject: CVS commit: pkgsrc/devel/opa
From: Leonardo Taccari
Date: 2024-12-26 18:32:19
Message id: 20241226173219.BA8C6FC1D@cvs.NetBSD.org
Log Message:
opa: Update to 1.0.0
Changes:
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:
- Using if for all rule definitions and contains for multi-value rules
is now mandatory, not just when using the rego.v1 import.
- Other new keywords (every, in) are available without any imports.
- Previously requirements that were only run in "strict mode" (like opa
check --strict) are now the default. Duplicate imports and imports
which shadow each other are no longer allowed.
- OPA 1.0 comes with a range of backwards compatibility features to aid
your migrations, please see the v0 compatibility guide if you must
continue to support v0 Rego.
For more information please see
<https://blog.openpolicyagent.org/announcing-opa-1-0-a-new-standard-for-policy-as-code-a6d8427ee828>.
Other changes:
- Improvements to memory allocations
- Wrap http.RoundTripper for SDK users
- Improvements to scientific notation parsing in units.parse
- Support customized buckets bundle_loading_duration_ns metric
- Test suite performance improvements
Files: