Bump github.com/open-policy-agent/opa from 1.19.1 to 1.20.1

[dependabot]

Bumps github.com/open-policy-agent/opa from 1.19.1 to 1.20.1.

Release notes

Sourced from github.com/open-policy-agent/opa's releases.

v1.20.1

This release includes a bug fix for a regression introduced in v1.20.0 in comparing a number to some float values. Thanks @​kmadan for reporting the issue and submitting a fix!

v1.20.0

This release contains a mix of new features and bug fixes. Notably:

• New Rego keywords: and and or, for combining conditions inside a single rule body
• allow_net now restricts remote JSON Schema $ref fetching from json.match_schema and json.verify_schema
• Coverage reports can now explain why a range is not covered
• Much faster partial evaluation for dynamically composed policies

New Rego keywords: and and or (#7602)

Rego gains two keywords for combining conditions inside a single rule body — a long-standing request, and one of the larger additions to the language in some time. and and or let control flow that previously had to be split across helper rules stay where it is read.

Before, a rule body that needed to succeed on one of several conditions meant extracting a rule:

package example
allow if {
input.method == "GET"
admin_or_public_owner
}
admin_or_public_owner if input.user.admin
admin_or_public_owner if {
input.user.owner
input.resource.public
}

Now:

package example
import future.keywords.and
import future.keywords.or
the and groups first, so this reads as:
an admin, or an owner of a public resource
allow if {
input.method == "GET"
</tr></table>

... (truncated)

Changelog

Sourced from github.com/open-policy-agent/opa's changelog.

1.20.1

This release includes a bug fix for a regression introduced in v1.20.0 in comparing a number to some float values. Thanks @​kmadan for reporting the issue and submitting a fix!

1.20.0

This release contains a mix of new features and bug fixes. Notably:

• New Rego keywords: and and or, for combining conditions inside a single rule body
• allow_net now restricts remote JSON Schema $ref fetching from json.match_schema and json.verify_schema
• Coverage reports can now explain why a range is not covered
• Much faster partial evaluation for dynamically composed policies

New Rego keywords: and and or (#7602)

Rego gains two keywords for combining conditions inside a single rule body — a long-standing request, and one of the larger additions to the language in some time. and and or let control flow that previously had to be split across helper rules stay where it is read.

Before, a rule body that needed to succeed on one of several conditions meant extracting a rule:

package example
allow if {
input.method == "GET"
admin_or_public_owner
}
admin_or_public_owner if input.user.admin
admin_or_public_owner if {
input.user.owner
input.resource.public
}

Now:

package example
import future.keywords.and
import future.keywords.or
the and groups first, so this reads as:
an admin, or an owner of a public resource
allow if {
</tr></table>

... (truncated)

Commits

• 72f30d6 Prepare v1.20.1 release
• ceb4bf2 ast: fix panic comparing a decimal zero with a non-integral number (#9099)
• 328ca09 Prepare v1.20.0 release (#9095)
• ce7ab30 Add Scanara to the OPA ecosystem page. (#9094)
• cbc0993 ast: Index rules with and/or expressions (#9063)
• 54bf329 fix loading absolute paths on Windows (#9055)
• 48310c6 format: Honor line breaks before explicit and/or operand bodies (#9086)
• a3953de build/release: Create new release tool (#8959)
• ec9536c format: converge object comprehension layout (#9076)
• 255adec ast: Fix future.keywords wildcard import not including the not keyword (#...
• Additional commits viewable in compare view