v0.8.0

0.8.0 (2024-11-15)

Added:

• feat: allow configuring the token endpoint (#137) - thanks @Divan009!
• feat: add per-HTTP request counter metric (#135)

Changed:

• refactor: remove SDK version for OpenTelemetry meter name (#134)

Fixed:

• fix: only send SDK method header from SDK wrapper methods (#142)
• fix: unable to pass retry_params (#144)
• fix: list users should send contextual tuples as a list (#147)
• fix: handle no models existing in read_latest_authorization_model (#147)

v0.7.2

0.7.2 (2024-09-22)

This release includes improvements to the OpenTelemetry configuration API introduced in the previous releases

• refactor: improve OpenTelemetry configuration (#127)

This release also includes fixes for several bugs identified in previous releases:

• fix: ensure max_parallel_requests is an int value in batch_check (#132)
• fix: inconsistency in 429 handling between sync/async client (#131)
• fix: ensure telemetry is reported when API exceptions are raised (#127)

v0.7.1

0.7.1 (2024-09-16)

This release includes fixes for several bugs identified in the previous release related to OpenTelemetry metrics reporting: (#124)

• fix: attribute values are now correctly exported as their intended types (previously, these were all sent as string values)
• fix: http_client_request_duration being reported in seconds rather than the intended milliseconds
• fix: sync client mistakenly passing the entire configuration (rather than just the OpenTelemetry configuration as intended) to queryDuration() and requestDuration()
• fix: some attributes may not have been exported as expected under some conditions
• fix: queryDuration() and requestDuration() may not have updated their histograms reliably when attr_http_client_request_duration or attr_http_server_request_duration (respectively) were not enabled (which is the default)

Please note that if you use third-party OpenTelemetry tooling to visualize the attributes mentioned above, you may need to update your queries to account for these changes.

v0.7.0

0.7.0 (2024-08-30)

• feat: enhancements to OpenTelemetry support (#120)

Breaking Changes

Note this introduces some breaking changes to our metrics:

1. fga-client.request.method is now in TitleCase to match the naming conventions in the Protos, e.g., Check, ListObjects, etc.
2. Due to possible high costs for attributes with high cardinality, we are no longer including the following attributes by default:
   • fga-client.user
   • http.client.request.duration
   • http.server.request.duration
     We added configuration options to allow you to set which specific metrics and attributes you care about in case the defaults don't work for your use case.

v0.6.1

0.6.1 (2024-07-31)

• feat: add support for specifying consistency when evaluating or reading (#113)
  Note: To use this feature, you need to be running OpenFGA v1.5.7+ with the experimental flag enable-consistency-params enabled.
  See the OpenFGA v1.5.7 release notes for details.

v0.6.0

0.6.0 (2024-06-28)

• feat: add OpenTelemetry metrics reporting (#107)

v0.5.0

0.5.0 (2024-06-17)

• fix: ClientTuple condition property type
• fix: list_users should accept FgaObject type
• fix: remove ReadAuthorizationModel calls from BatchCheck and writes
• chore!: remove excluded users from ListUsers response

v0.4.3

0.4.3 (2024-06-07)

• feat: support for list users

v0.4.2

0.4.2 (2024-04-04)

• feat: support for modular models metadata
• feat: support auto-retry of failed network requests
• refactor: remove Python 2 code
• fix: limit the number of network retries
• fix: Configuration class api_scheme, min_wait_in_ms and disabled_client_side_validations validation issues
• chore: update aiohttp to 3.9.2
• chore: update black to 24.3.0

v0.4.1

0.4.1 (2024-02-13)

• feat: support api_url configuration option and deprecate api_scheme and api_host
• fix: use correct content type for token request