build(deps): bump github.com/openfga/openfga from 1.5.6 to 1.5.8

[dependabot]

Bumps github.com/openfga/openfga from 1.5.6 to 1.5.8.

Release notes

Sourced from github.com/openfga/openfga's releases.

v1.5.8

Added

• Performance improvements for Check API:
  • introduce an optimization when the input request relation is pointing to a computed relation #1793
  • batch calls that compute membership checks and start processing them earlier #1804
• Logging number of cache hits for each subproblem of each authorization model for Check API calls. Enabled with the OPENFGA_CHECK_TRACKER_ENABLED flag. #1785
• Aliases for issuers and subject validation in OIDC AuthN mode using OPENFGA_AUTHN_OIDC_ISSUER_ALIASES and OPENFGA_AUTHN_OIDC_SUBJECTS respectively #1784 Thanks @​Code2Life!
• Dispatch Throttling for our ListUsers API. This can be enabled using OPENFGA_LIST_USERS_DISPATCH_THROTTLING_ENABLED and the env variables below. #1658
  • OPENFGA_LIST_USERS_DISPATCH_THROTTLING_THRESHOLD - The number of dispatches allowed before throttling is triggered
  • OPENFGA_LIST_USERS_DISPATCH_THROTTLING_MAX_THRESHOLD - The maximum number of dispatches allowed before the request is rejected
  • OPENFGA_LIST_USERS_DISPATCH_THROTTLING_FREQUENCY - The frequency at which the deprioritized throttling queue is processed
• Support sending contextual tuples in the Write Assertions API. #1821

Fixed

• address "expected exactly one terminal relation for fast path, received {num}" error during Check for models with type restrictions with and without a condition or with multiple conditions. #1814

v1.5.7

Added

• Support requesting a different consistency option per request in Check, Expand, ListObjects, ListUsers, and Read #1764
  • This is currently experimental and needs to be enabled by configuring OPENFGA_EXPERIMENTALS=enable-consistency-params or passing --experimentals enable-consistency-params to openfga run.
  • When HIGHER_CONSISTENCY is requested, OpenFGA will skip the check resolver cache. For storage implementors it is recommended to skip any caching and perform a stronger read if HIGHER_CONSISTENCY is requested. This can be accessed in the Consistency options provided to the relevant methods of the storage interface.
• Start publishing images to ghcr.io/openfga/openfga as alternative to DockerHub #1775 - Thanks @​JAORMX!
• Performance improvements for parent child relations in Check #1765
• Performance improvement in Check: computed relations don't consume from the resolution depth quota, don't trigger additional goroutines, and don't get cached #1786

Changed

• Update to Go 1.22 in container image #1776 - Thanks @​tranngoclam!

Breaking Changes ⚠️

[!NOTE] The following breaking changes are related to the storage interface. If you are not implementing a storage adaptor, then there are these changes should not impact your usage of OpenFGA.

Removal of PaginationOptions in favour of a per-method Options type #1732

The options parameter of type PaginationOptions has been replaced with a per-method type that contains a Pagination field that contains this data in the following methods:

• ReadAuthorizationModels - Type is ReadAuthorizationModelsOptions
• ListStores - Type is ListStoresOptions
• ReadChanges - Type is ReadChangesOptions
• ReadPage - Type is ReadPageOptions

Introduction of new Options types to certain methods in the storage interface to facilitate consistency data #1750

The following methods have had an options parameter introduced to the method signature to include consistency data, or the existing options parameter has been expanded to hold consistency data.

This consistency data should be used to help determine whether any form of caching should be used as part of the read performed by the storage adapter.

... (truncated)

Changelog

Sourced from github.com/openfga/openfga's changelog.

[1.5.8] - 2024-08-07

Full changelog

Added

• Performance improvements for Check API:
  • introduce an optimization when the input request relation is pointing to a computed relation #1793
  • batch calls that compute membership checks and start processing them earlier #1804
• Logging number of cache hits for each subproblem of each authorization model for Check API calls. Enabled with the OPENFGA_CHECK_TRACKER_ENABLED flag. #1785
• Aliases for issuers and subject validation in OIDC AuthN mode using OPENFGA_AUTHN_OIDC_ISSUER_ALIASES and OPENFGA_AUTHN_OIDC_SUBJECTS respectively #1784 Thanks @​Code2Life!
• Dispatch Throttling for our ListUsers API. This can be enabled using OPENFGA_LIST_USERS_DISPATCH_THROTTLING_ENABLED and the env variables below. #1658
  • OPENFGA_LIST_USERS_DISPATCH_THROTTLING_THRESHOLD - The number of dispatches allowed before throttling is triggered
  • OPENFGA_LIST_USERS_DISPATCH_THROTTLING_MAX_THRESHOLD - The maximum number of dispatches allowed before the request is rejected
  • OPENFGA_LIST_USERS_DISPATCH_THROTTLING_FREQUENCY - The frequency at which the deprioritized throttling queue is processed
• Support sending contextual tuples in the Write Assertions API. #1821

Fixed

• address "expected exactly one terminal relation for fast path, received {num}" error during Check for models with type restrictions with and without a condition or with multiple conditions. #1814

[1.5.7] - 2024-07-25

Added

• Support requesting a different consistency option per request in Check, Expand, ListObjects, ListUsers, and Read #1764
  • This is currently experimental and needs to be enabled by configuring OPENFGA_EXPERIMENTALS=enable-consistency-params or passing --experimentals enable-consistency-params to openfga run.
  • When HIGHER_CONSISTENCY is requested, OpenFGA will skip the check resolver cache. For storage implementors it is recommended to skip any caching and perform a stronger read if HIGHER_CONSISTENCY is requested. This can be accessed in the Consistency options provided to the relevant methods of the storage interface.
• Start publishing images to ghcr.io/openfga/openfga as alternative to DockerHub #1775 - Thanks @​JAORMX!
• Performance improvements for parent child relations in Check #1765
• Performance improvement in Check: computed relations don't consume from the resolution depth quota, don't trigger additional goroutines, and don't get cached #1786

Changed

• Update to Go 1.22 in container image #1776 - Thanks @​tranngoclam!

Breaking Changes ⚠️

[!NOTE] The following breaking changes are related to the storage interface. If you are not implementing a storage adaptor, then there are these changes should not impact your usage of OpenFGA.

Removal of PaginationOptions in favour of a per-method Options type #1732

The options parameter of type PaginationOptions has been replaced with a per-method type that contains a Pagination field that contains this data in the following methods:

• ReadAuthorizationModels - Type is ReadAuthorizationModelsOptions
• ListStores - Type is ListStoresOptions
• ReadChanges - Type is ReadChangesOptions
• ReadPage - Type is ReadPageOptions

Introduction of new Options types to certain methods in the storage interface to facilitate consistency data #1750

... (truncated)

Commits

• 496c72d add v1.5.8 release notes to CHANGELOG (#1822)
• 0779401 feat: support Contextual Tuples in Assertions API (#1821)
• 282e346 chore(deps): bump the dependencies group across 1 directory with 6 updates (#...
• 8dbdede fix: do not error if multiple terminal relations exist during fast-path (#1817)
• 3b8039d perf(Check): stream userset results (#1804)
• d31a27f chore: remove panics if typesystem missing in ctx (#1809)
• 37edd89 perf: reduce proto conversions (#1818)
• ffe46e1 fix: connected types consolidate type definitions with and without a conditio...
• 817293c feat: ListUsers dispatch throttling (#1658)
• fb78181 fix: proper nesting of spans in Check API if computed usersets (#1815)
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.