Skip to content

Releases: pydantic/terraform-provider-logfire

v0.1.13

Choose a tag to compare

@github-actions github-actions released this 21 Jul 13:06
30c6bf8
Merge pull request #46 from pydantic/slo-channel-seeding

logfire_slo: seed the generated burn-rate alerts' channels at creation

v0.1.12

Choose a tag to compare

@github-actions github-actions released this 15 Jul 16:57
5c53f47
Add `environments` attribute to the `logfire_alert` resource (#45)

* Add environments attribute to the logfire_alert resource

Allow scoping an alert's query to specific deployment environments via a
new optional `environments` set-of-strings attribute, matching the
`environments` field on the Logfire alerts API. Omitting the attribute
(or setting it empty) keeps the current behavior of evaluating the query
against all environments.

- Add `environments` to the `AlertCreate`/`AlertUpdate`/`AlertRead`
  client payloads.
- Map the attribute through create/read/update, keeping the attribute
  null when omitted so an unfiltered alert (API returns `[]`) round-trips
  without spurious diffs, and clearing the filter server-side when the
  attribute is removed from config.
- Cover the mapping in unit tests and extend the alert acceptance test
  with set/unset steps.
- Regenerate docs and update the example.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019M73jzqCewwcc6pmvVWPeg

* Apply suggestions from code review

Co-authored-by: Victorien <65306057+Viicos@users.noreply.github.com>

* Regenerate docs and terraform fmt example after review suggestions

The review suggestions updated the environments schema description and
removed the comment in the alert example, which changed the terraform
fmt alignment group for the whole attribute block. Re-run `make
generate` so the generate CI check passes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019M73jzqCewwcc6pmvVWPeg

* Only clear environments on update when the planned value is null

Mirror the null/unknown handling used for description and visibility in
project_resource.go: gate on the planned value not being unknown, then
clear the filter only when it is explicitly null. Previously an unknown
planned value fell into the clearing branch and would wipe the filter.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019M73jzqCewwcc6pmvVWPeg

* Adapt the SLO resource to the scope-based API and add metric_aggregation

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Nicola Martino <nicola@pydantic.dev>

v0.1.11

Choose a tag to compare

@github-actions github-actions released this 14 Jul 12:35
a2d0f6d
Merge pull request #43 from pydantic/slo-resource

Add experimental logfire_slo resource

v0.1.10

Choose a tag to compare

@github-actions github-actions released this 02 Jul 15:57
v0.1.10

v0.1.9

Choose a tag to compare

@github-actions github-actions released this 19 May 19:37
v0.1.9

v0.1.8

Choose a tag to compare

@github-actions github-actions released this 16 May 14:45
v0.1.8

v0.1.7

Choose a tag to compare

@github-actions github-actions released this 15 May 20:21
v0.1.7

v0.1.6

Choose a tag to compare

@github-actions github-actions released this 08 Apr 15:03
Fix dashboard definition custom type equality

v0.1.5

Choose a tag to compare

@github-actions github-actions released this 07 Apr 20:46
Prepare v0.1.5 release

v0.1.4

Choose a tag to compare

@github-actions github-actions released this 01 Apr 14:08
Prepare v0.1.4 release