fix(f3): probe infisical health over tailnet #313

Merged
pdurlej merged 1 commit from codex/f3/infisical-health-probe into main 2026-05-17 02:34:39 +02:00
Collaborator

Canary status: missing — module manifest health-probe fix; rely on required Forgejo checks before merge

Canary Context Pack

Product story

F3 stateful smoke for Infisical should test the actual reachable health surface. The current manifest checks a public URL that returns 403 from outside the Tailnet, while Infisical is healthy and available through the Tailnet allowlist.

What changed

  • Updated infisical HTTP health probe from public /health to tailnet-https://infisical.pdurlej.com/api/status.
  • Updated the acceptance criterion to match the Tailnet health endpoint.

Why it changed

F3 run #1089 failed after backup because https://infisical.pdurlej.com/health returns 403 through the public path. Runtime evidence shows Tailnet-resolved /api/status returns HTTP 200 and the container healthcheck is green.

Files touched

  • modules/infisical/module.yaml

Runtime evidence

  • home-platform-infisical-1 is running healthy.
  • Public https://infisical.pdurlej.com/health returns HTTP 403.
  • Tailnet-resolved https://infisical.pdurlej.com/api/status returns HTTP 200.
  • Container-local http://127.0.0.1:8080/api/status returns Ok with Redis configured.

Known constraints

This is probe metadata only. It does not change Infisical runtime, routing, secrets, or exposure policy.

Explicit out-of-scope

  • No compose changes.
  • No Infisical restart.
  • No secret reads.

Requested decision

Merge so the already-backed-up Infisical F3 smoke can be retried with the correct health probe.

Merge blockers

  • strict-v2 validation failure
  • health probe contract regression

Spec sources read

  • modules/infisical/module.yaml — target manifest
  • modules/honcho-api/module.yaml — Tailnet health URL pattern
  • compose/apps/compose.yaml — Infisical Traefik middleware and container healthcheck

Verification

control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/infisical/module.yaml
control-plane/.venv/bin/pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_health_phase3.py -q
git diff --check

Refs: #142

Canary status: missing — module manifest health-probe fix; rely on required Forgejo checks before merge ## Canary Context Pack ### Product story F3 stateful smoke for Infisical should test the actual reachable health surface. The current manifest checks a public URL that returns 403 from outside the Tailnet, while Infisical is healthy and available through the Tailnet allowlist. ### What changed - Updated `infisical` HTTP health probe from public `/health` to `tailnet-https://infisical.pdurlej.com/api/status`. - Updated the acceptance criterion to match the Tailnet health endpoint. ### Why it changed F3 run #1089 failed after backup because `https://infisical.pdurlej.com/health` returns 403 through the public path. Runtime evidence shows Tailnet-resolved `/api/status` returns HTTP 200 and the container healthcheck is green. ### Files touched - `modules/infisical/module.yaml` ### Runtime evidence - `home-platform-infisical-1` is `running healthy`. - Public `https://infisical.pdurlej.com/health` returns HTTP 403. - Tailnet-resolved `https://infisical.pdurlej.com/api/status` returns HTTP 200. - Container-local `http://127.0.0.1:8080/api/status` returns `Ok` with Redis configured. ### Known constraints This is probe metadata only. It does not change Infisical runtime, routing, secrets, or exposure policy. ### Explicit out-of-scope - No compose changes. - No Infisical restart. - No secret reads. ### Requested decision Merge so the already-backed-up Infisical F3 smoke can be retried with the correct health probe. ### Merge blockers - strict-v2 validation failure - health probe contract regression ## Spec sources read - `modules/infisical/module.yaml` — target manifest - `modules/honcho-api/module.yaml` — Tailnet health URL pattern - `compose/apps/compose.yaml` — Infisical Traefik middleware and container healthcheck ## Verification ```bash control-plane/.venv/bin/python -m platformctl.cli validate --strict-v2 modules/infisical/module.yaml control-plane/.venv/bin/pytest control-plane/platformctl/tests/test_validate.py control-plane/platformctl/tests/test_health_phase3.py -q git diff --check ``` Refs: #142
fix(f3): probe infisical health over tailnet
All checks were successful
base-is-main / guard (pull_request) Successful in 1s
canary-required / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
platformctl plan / auto-apply scope (pull_request) Successful in 18s
canary-required / canary (pull_request) Successful in 13s
patchwarden-pr-sanity / sanity (pull_request) Successful in 18s
5d397fd2d3
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!313
No description provided.