Compare commits

..
1 Commits
Author SHA1 Message Date
implementer 25248461e0 docs: document the redacted resolved-configuration log in the non-container guide (E00-S04-T03)
CI / Frozen lockfile install (pull_request) Successful in 50s
CI / Secrets not embedded (E00-S02-T08) (pull_request) Successful in 29s
CI / Database-postgres import isolation (E00-S03-T02) (pull_request) Successful in 33s
CI / Migration ledger (E00-S03-T03) (pull_request) Successful in 44s
CI / Migration advisory lock (E00-S03-T04) (pull_request) Successful in 46s
CI / Migration failure diagnostic (E00-S03-T05) (pull_request) Successful in 44s
CI / App readiness after migrations (E00-S03-T06) (pull_request) Successful in 1m12s
CI / Field-specific startup errors (E00-S04-T02) (pull_request) Successful in 1m12s
CI / Secret redaction from logs (E00-S04-T03) (pull_request) Successful in 1m15s
CI / TypeBox/Ajv config schema (E00-S04-T01) (pull_request) Successful in 53s
CI / Compose config (E00-S03-T01) (pull_request) Successful in 25s
2026-08-30 03:52:55 +00:00
+4 -4
View File
@@ -17,10 +17,10 @@
* a secret value (e.g. an error message carrying a connection string) is
* redacted even when the value was not redacted by field.
*
* Both feed the server's redacting logger (the `createLogger` in
* `apps/server/src/index.ts`), so secret values never reach stdout/stderr —
* the acceptance criteria: "secrets automatically redact from logs", "log
* output contains no secret values".
* Both feed the server's redacting logger (`apps/server/src/logger.ts`), so
* secret values never reach stdout/stderr — the acceptance criteria:
* "secrets automatically redact from logs", "log output contains no secret
* values".
*
* Rollback note from the issue: revert the redaction changes.
*/