Leonardo Cecchi aaf6120eaa fix: classify WAL restore errors with precise gRPC statuses (#927) ... Map each restorer sentinel to the gRPC status that best reflects whether the operator should retry: - ErrWALNotFound -> NotFound (terminal) - ErrInvalidWalName -> InvalidArgument (terminal) - ErrConnectivity -> Unavailable (retry) - ErrGeneric -> Unavailable (retry) - anything else -> Internal (terminal) Previously every non-NotFound failure was returned verbatim, leaving the operator unable to tell transient blips apart from terminal conditions like a malformed WAL name. Signed-off-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Tao Li <tao.li@enterprisedb.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Tao Li <tao.li@enterprisedb.com>		2026-06-03 11:25:07 +02:00
..
crd	fix: classify WAL restore errors with precise gRPC statuses (#927)	2026-06-03 11:25:07 +02:00
default	feat(rbac)!: prefix all resource names to avoid cluster conflicts (#593)	2025-10-27 15:08:11 +01:00
manager	feat: operator plugin and manifests (#18)	2024-10-01 15:40:48 +02:00
network-policy	chore: scaffold (#2)	2024-09-26 11:52:56 +02:00
prometheus	chore: scaffold (#2)	2024-09-26 11:52:56 +02:00
rbac	feat(rbac)!: prefix all resource names to avoid cluster conflicts (#593)	2025-10-27 15:08:11 +01:00
samples	feat: sidecar role and rolebinding (#23)	2024-10-02 15:03:07 +02:00