Bump github.com/open-policy-agent/opa from 0.58.0 to 0.60.0

[dependabot]

Bumps github.com/open-policy-agent/opa from 0.58.0 to 0.60.0.

Release notes

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

v0.59.0

This release adds tooling to help prepare existing policies for the upcoming OPA 1.0 release. It also contains a mix of improvements, bugfixes and security fixes for third-party libraries.

NOTES:

• All published OPA images now run with a non-root uid/gid. The uid:gid is set to 1000:1000 for all images. As a result there is no longer a need for the -rootless image variant and hence it will not be published as part of future releases. This change is in line with container security best practices. OPA can still be run with root privileges by explicitly setting the user, either with the --user argument for docker run, or by specifying the securityContext in the Kubernetes Pod specification.

Rego v1

The upcoming release of OPA 1.0, which will be released at a future date, will introduce breaking changes to the Rego language. Most notably:

• the keywords that currently must be imported through import future.keywords into a module before use will be part of the Rego language by default, without the need to first import them.
• the if keyword will be required before the body of a rule.
• the contains keyword will be required when declaring a multi-value rule (partial set rule).
• deprecated built-in functions will be removed.

This current release (0.59.0) introduces a new --rego-v1 flag to the opa fmt and opa check commands to facilitate the transition of existing policies to be compatible with the 1.0 syntax.

When used with opa fmt, the --rego-v1 flag will format the module(s) according to the new Rego syntax in OPA 1.0. Formatted modules are compatible with both the current version of OPA and 1.0. Modules using deprecated built-ins will terminate formatting with an error. Future versions of OPA will support rewriting applicable function calls with equivalent Rego compatible with 1.0.

When used with opa check, the --rego-v1 flag will check that the modules are compatible with both the current version of OPA and 1.0.

Relevant Changes

• cmd: Adding --rego-v1 flag to check cmd (#6429) authored by @​johanfylling
• cmd & format: Adding rego-v1 mode to opa fmt (#6297) authored by @​johanfylling
• ast: Adding capability feature for the rego.v1 import (#6375) (authored by @​johanfylling)
• ast: Skip if keyword requirement for default rule (rego.v1) (#6356) authored by @​ashutosh-narkar
• rego.v1: Fixing erroneous missing value assignment error (#6364) authored by @​johanfylling
• rego.v1: Improving support for rules with chained bodies (#6370) authored by @​johanfylling
• ast: Add rego.v1 import (#6247) introduced in OPA 0.58.0, authored by @​johanfylling

Runtime, Tooling, SDK

• ast: Adding rule_head_refs capabilities feature flag (#6334) authored by @​johanfylling
• build: Remove rootless image variant (#4295) authored by @​ashutosh-narkar
• discovery: Make status updates non blocking (#6345) (#6343) authored by @​charlieegan3
• plugins/rest: Masks X-AMZ-SECURITY-TOKEN header in decision logs (#5848) authored by @​colinjlacy reported by @​jwineinger
• wasm: Fix re2 bug (#6376) authored by @​srenatus reported by @​sandhose
• ast: Add ExcludeLocationFile JSON marshalling option (#6398) (authored by @​anderseknert)
• cmd: Add options to the filter to only load rego files (#6317) authored by @​tjons
• ast: Add minimum compatible version computation to compiler (#6348) authored by @​tsandall

... (truncated)

Changelog

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

0.60.0

Runtime, Tooling, SDK

• OPA can be run in 1.0 compatibility mode by using the new --v1-compatible flag. When this mode is enabled, the current release of OPA will behave as OPA v1.0 will eventually behave by default. This flag is currently supported on the build, check, fmt, eval and test commands (#6478) authored by @​johanfylling
• Extend the telemetry report to include the minimum compatible version of policies loaded into OPA (#6361) co-authored by @​srenatus and @​ashutosh-narkar
• server: Support fsnotify based reloading of certificate, key and CA cert pool when they change on disk (#5788) authored by @​charlieegan3
• Add option on the unit test runner to surface builtin errors. This should help with debugging errors generated while running unit tests (#6489) authored by @​jalseth
• Fix issue in opa fmt where the assignment operator and term in the rule head of chain rules are removed from the re-written rule head (#6467) authored by @​anderseknert
• cmd/fmt: Replace dependency on diff tool with an external golang library function (#6284) authored by @​colinjlacy

Topdown and Rego

• topdown/providers: Preserve user provided http headers in the providers.aws.sign_req builtin command (#6456) authored by @​c2zwdjnlcg
• rego: Allow custom builtin function registration to provide a description for the builtin (#6449) authored by @​lcarva
• ast+cmd: Allow bundle to contain calls to unknown functions when inspected (#6457) authored by @​johanfylling

Docs

• Add section on the changes proposed for a future OPA v1.0 and update Rego examples to be OPA v1.0 compliant(#6453) authored by @​johanfylling
• Clarify behavior of the sprintf builtin command when used with the %T marker (#6487) authored by @​lcarva

Website + Ecosystem

• Ecosystem: Digger (#6464) authored by @​anderseknert

Miscellaneous

• Update Makefile to allow custom GOFLAGS to be provided to the golang executable (#6458) authored by @​cova-fe
• Dependency updates; notably:
  • bump golang 1.21.4 -> 1.21.5 (#6460) authored by @​srenatus
  • bump aquasecurity/trivy-action from 0.14.0 to 0.16.0
  • bump github.com/containerd/containerd from 1.7.9 to 1.7.11
  • bump google.golang.org/grpc from 1.59.0 to 1.60.1
  • bump github.com/google/uuid from 1.4.0 to 1.5.0

0.59.0

This release adds tooling to help prepare existing policies for the upcoming OPA 1.0 release. It also contains a mix of improvements, bugfixes and security fixes for third-party libraries.

NOTES:

• All published OPA images now run with a non-root uid/gid. The uid:gid is set to 1000:1000 for all images. As a result there is no longer a need for the -rootless image variant and hence it will not be published as part of future releases. This change is in line with container security best practices. OPA can still be run with root privileges by explicitly setting the user, either with the --user argument for docker run, or by specifying the securityContext in the Kubernetes Pod specification.

Rego v1

The upcoming release of OPA 1.0, which will be released at a future date, will introduce breaking changes to the Rego language. Most notably:

• the keywords that currently must be imported through import future.keywords into a module before use will be part of the Rego language by default, without the need to first import them.
• the if keyword will be required before the body of a rule.
• the contains keyword will be required when declaring a multi-value rule (partial set rule).

... (truncated)

Commits

• a1a2ae3 Prepare v0.60.0 release
• 9f63fdb ast+cmd: Allowing bundle to contain calls to unknown functions when inspected...
• f04636a docs: Update generated CLI docs
• 38c2f0c Adding --v1-compatible flag to build, opa eval (#6478)
• 84751f0 build(deps): bump google.golang.org/grpc from 1.60.0 to 1.60.1
• 979e626 internal/presentation: cleanup location handling (#6498)
• b85eb64 .github/workflows: Update name of the checkout action token
• 24f09cd .github/workflows: Update checkout action token
• ba46112 Docs: Explain %T behavior of sprintf
• 6d26f98 feat: Support raising builtin errors in the test runner
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)