Azure / ShieldGuard

Enables best security practices for your project from day zero.
MIT License
8 stars 6 forks source link

chore(deps): bump github.com/open-policy-agent/opa from 0.55.0 to 0.57.0 in /sg #75

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps github.com/open-policy-agent/opa from 0.55.0 to 0.57.0.

Release notes

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

v0.57.0

This release contains an updated Rego syntax to allow general references in rule heads, and a mix of new features and bugfixes.

Support for General References in Rule Heads

In OPA 0.56.0, we introduced support for general references in rule heads as an experimental feature. It has now graduated to a fully supported feature, and is no longer experimental.

A general reference is a reference with variables at arbitrary locations. In Rego, partial rules are used for generating sets and objects. In previous versions of OPA, variables were only allowed in the very last position in the rule's reference. Now, Rego has been expanded to allow rules to be declared with general references in their head, with variables at arbitrary locations. This allows for generating nested dynamic object structures:

package example

import future.keywords

Converting a flat list of users to a mapping by "role" and then "id".

users_by_role[role][id] := user if { some user in data.users id := user.id role := user.role }

Explicit "admin" key override to the above mapping.

users_by_role.admin[id] := user if { some user in data.admins id := user.id }

Leaf entries can be multi-value.

users_by_country[country] contains user.id if { some user in data.users country := user.country }

See the documentation for more information.

Authored by @​johanfylling.

Runtime, Tooling, SDK

Topdown and Rego

... (truncated)

Changelog

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

0.57.0

This release contains an updated Rego syntax to allow general references in rule heads, and a mix of new features and bugfixes.

Support for General References in Rule Heads

In OPA 0.56.0, we introduced support for general references in rule heads as an experimental feature. It has now graduated to a fully supported feature, and is no longer experimental.

A general reference is a reference with variables at arbitrary locations. In Rego, partial rules are used for generating sets and objects. In previous versions of OPA, variables were only allowed in the very last position in the rule's reference. Now, Rego has been expanded to allow rules to be declared with general references in their head, with variables at arbitrary locations. This allows for generating nested dynamic object structures:

package example

import future.keywords

Converting a flat list of users to a mapping by "role" and then "id".

users_by_role[role][id] := user if { some user in data.users id := user.id role := user.role }

Explicit "admin" key override to the above mapping.

users_by_role.admin[id] := user if { some user in data.admins id := user.id }

Leaf entries can be multi-value.

users_by_country[country] contains user.id if { some user in data.users country := user.country }

See the documentation for more information.

Authored by @​johanfylling.

Runtime, Tooling, SDK

Topdown and Rego

... (truncated)

Commits
  • c2f42aa Prepare v0.57.0 release (#6256)
  • c36a605 docs: Documenting general refs in rule heads (#6244)
  • 974586e server: Add test case for bundle update - query API handler scenario
  • c5314e3 Removing EXPERIMENTAL_GENERAL_RULE_REFS feature flag (#6252)
  • c9d1a8d planner: Adding support for general ref rule heads (#6235)
  • 391cb0c Add rego-cpp to OPA Ecosystem
  • 83a295f [docs] Use links on support page (#6249)
  • 919b290 plugins: Surface AWS authentication error details
  • 276702f Updating all vars in rule ref
  • b07e60a nightly: skip Fri/Sat night (#6242)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)