Skip to content

Phase 26 F3: remove fabricated data — kubecost/asean/audit fail-closed - #73

Merged
munisp merged 1 commit into
mainfrom
phase26/f3-fabrication
Oct 3, 2026
Merged

munisp merged 1 commit into
mainfrom
phase26/f3-fabrication

Conversation

@munisp

@munisp munisp commented Oct 3, 2026

Copy link
Copy Markdown
Owner

G5b remediation. kubecost-svc proxies the real Kubecost Allocation API (KUBECOST_URL required, 503 fail-closed on upstream failure; all hardcoded cost figures removed). asean-sw-service persists to asean_sw_messages via pgx/v5 (DATABASE_URL fail-closed; simulated ACKs and ping latency removed — real gateway dispatch/probes). audit-service persists to post_clearance_audits via pgx/v5 (DATABASE_URL fail-closed; discrepancy/penalty 404 when no audit row exists). Route paths + JSON shapes preserved; no seeds; no schema/migration changes; go build ./... clean-cache exit 0 for all three services.

…asean-sw-service, audit-service — fail-closed

- kubecost-svc: all cost figures now proxied from the real Kubecost Allocation API (KUBECOST_URL required, log.Fatal otherwise); upstream failure -> 503 with honest error; removed mock tenant registry, rand-based cost generators and all hardcoded figures
- asean-sw-service: pgx/v5 persistence to existing asean_sw_messages table (DATABASE_URL required, fail-closed startup, ping); removed simulated ACKs and in-memory store; connection tests are real HTTP probes with measured latency; dispatch failure -> 502, message persisted as failed
- audit-service: pgx/v5 persistence to existing post_clearance_audits table (DATABASE_URL required, fail-closed startup, ping); selected audits inserted as real rows; discrepancy/penalty update existing audits and 404 when absent; stats include real DB counts; /health does SELECT 1
- No seed rows, no fabricated fallbacks; HTTP route paths and JSON shapes preserved; no gRPC added; drizzle schema and migrations untouched
@munisp
munisp merged commit 67f5019 into main Oct 3, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant