Skip to content

Commit 6ffc276

Browse files
authored
fix: Use correct priority for field override "for" (#10)
Details: - Use override if defined - Otherwise use what is defined inside the prometheus alert file - If nothing of both is defined, use `null`
1 parent 126a846 commit 6ffc276

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

grafana_alert.tf

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,13 @@ resource "grafana_rule_group" "this" {
1919
for_each = { for rule in each.value.rules : rule.alert => rule }
2020

2121
content {
22-
name = rule.value.alert
23-
for = try(var.overrides[rule.value.alert].for, rule.value.for, null)
22+
name = rule.value.alert
23+
for = try(
24+
coalesce(
25+
try(var.overrides[rule.value.alert].for, null), # Is there an override?
26+
try(rule.value.for, null) # Is it defined inside the prometheus alert?
27+
), null) # If nothing of both is defined, use `null`
28+
2429
condition = "ALERTCONDITION"
2530

2631
annotations = {

0 commit comments

Comments
 (0)