You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(logs_alert): read destinations from the alert, not their own endpoint
PostHog #84509 dropped the separate destinations list endpoint and returns
the same groups on the alert read instead. A GET to the destinations path
now answers 405, so refresh and import would fail against the deployed API.
The list is a field on the alert, so it is not paginated. That removes the
listAllWithStatus helper this branch added for it.
Copy file name to clipboardExpand all lines: docs/resources/logs_alert_destination.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ subcategory: ""
5
5
description: |-
6
6
Manage where a log alert https://posthog.com/docs/logs/alerts sends its notifications. A posthog_logs_alert with no destination still evaluates and reports its state, but notifies nobody.
7
7
~> Every attribute forces replacement. PostHog has no update endpoint for destinations, so changing a channel or a URL destroys the destination and creates a new one. There is a short window during the apply where the alert has no destination and would notify nobody if it fired.
8
-
Each resource represents one user-visible destination. PostHog implements that destination as a group of hog functions, one per alert transition (firing, resolved, errored, auto-disabled), sharing the configuration below. The group has no id of its own, so this resource's id is the group's hog_function_ids, sorted and joined by commas. Those hog functions are owned by the alert: posthog_hog_function cannot create, update, or delete them. Terraform reads, creates, and deletes each managed group through the alert's dedicated destinations API.
8
+
Each resource represents one user-visible destination. PostHog implements that destination as a group of hog functions, one per alert transition (firing, resolved, errored, auto-disabled), sharing the configuration below. The group has no id of its own, so this resource's id is the group's hog_function_ids, sorted and joined by commas. Those hog functions are owned by the alert: posthog_hog_function cannot create, update, or delete them. Terraform creates and deletes each managed group through the alert's destinations API, and reads it back from the alert itself.
9
9
---
10
10
11
11
# posthog_logs_alert_destination (Resource)
@@ -14,7 +14,7 @@ Manage where a [log alert](https://posthog.com/docs/logs/alerts) sends its notif
14
14
15
15
~> **Every attribute forces replacement.** PostHog has no update endpoint for destinations, so changing a channel or a URL destroys the destination and creates a new one. There is a short window during the apply where the alert has no destination and would notify nobody if it fired.
16
16
17
-
Each resource represents one user-visible destination. PostHog implements that destination as a group of hog functions, one per alert transition (firing, resolved, errored, auto-disabled), sharing the configuration below. The group has no id of its own, so this resource's `id` is the group's `hog_function_ids`, sorted and joined by commas. Those hog functions are owned by the alert: `posthog_hog_function` cannot create, update, or delete them. Terraform reads, creates, and deletes each managed group through the alert's dedicated destinations API.
17
+
Each resource represents one user-visible destination. PostHog implements that destination as a group of hog functions, one per alert transition (firing, resolved, errored, auto-disabled), sharing the configuration below. The group has no id of its own, so this resource's `id` is the group's `hog_function_ids`, sorted and joined by commas. Those hog functions are owned by the alert: `posthog_hog_function` cannot create, update, or delete them. Terraform creates and deletes each managed group through the alert's destinations API, and reads it back from the alert itself.
0 commit comments