From cf42042cbae8bbc15b2c24be32ac24ec6f91432f Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Sun, 28 Jun 2026 16:58:49 +0000 Subject: [PATCH] monitoring: re-trigger apply to persist state after CI cancel-race No-op comment touch in loki.tf to force a clean `terragrunt apply monitoring`. The pfSense egress-monitoring apply (commit 7fe2d978, CI pipeline #414) was cancelled by a newer push and SIGKILLed mid-helm-upgrade: the live resources applied (probes green, rules loaded) but the Terraform state write and the helm release finalize were lost, leaving the prometheus release stuck in pending-upgrade (manually unstuck). This commit re-applies the unchanged monitoring stack so state matches live, with zero resource changes. Co-Authored-By: Claude Opus 4.8 --- stacks/monitoring/modules/monitoring/loki.tf | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/stacks/monitoring/modules/monitoring/loki.tf b/stacks/monitoring/modules/monitoring/loki.tf index 9ecd9888..47ad6ba4 100644 --- a/stacks/monitoring/modules/monitoring/loki.tf +++ b/stacks/monitoring/modules/monitoring/loki.tf @@ -126,6 +126,12 @@ resource "kubernetes_daemon_set_v1" "sysctl-inotify" { # atomic = true # } +# 2026-06-28: trivial touch to re-trigger a clean `terragrunt apply monitoring` +# so TF state is persisted after CI pipeline #414 (the pfSense egress-monitoring +# apply, commit 7fe2d978) was cancel-raced by a newer push and SIGKILLed +# mid-helm-upgrade: the live resources applied but the state write + helm-release +# finalize were lost (the stuck pending-upgrade release was manually unstuck). +# See docs/runbooks/pfsense-egress.md and the Woodpecker cancel-previous gotcha. resource "kubernetes_config_map" "loki_alert_rules" { metadata { name = "loki-alert-rules"