fix: clarify durable postgres blocker diagnostics
This commit is contained in:
@@ -59,10 +59,10 @@ checks:
|
||||
- read readiness against the runtime tables used by audit and evidence
|
||||
queries.
|
||||
|
||||
If DB auth, schema, migration, or read readiness is missing, `/health/live`
|
||||
If DB SSL negotiation, auth, schema, migration, or read readiness is missing, `/health/live`
|
||||
stays degraded with `runtime.durable: false`, `runtime.durableRequested: true`,
|
||||
and a runtime blocker such as `runtime_durable_adapter_auth_blocked`,
|
||||
`runtime_durable_adapter_schema_blocked`, or
|
||||
and a runtime blocker such as `runtime_durable_adapter_ssl_blocked`,
|
||||
`runtime_durable_adapter_auth_blocked`, `runtime_durable_adapter_schema_blocked`, or
|
||||
`runtime_durable_adapter_migration_blocked`. Fixture data and env presence are
|
||||
never promoted to `runtime.liveRuntimeEvidence`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user