Scooby HuskyandClaude Sonnet 5 d6e8c2aa2d Optimize vault-restore: don't wait on condition=Ready (verified working already) ...

Confirmed end-to-end tonight: condition=Ready correctly times out every
cycle since Vault can't be Ready while sealed (the unseal step comes
right after this wait) - harmless via the existing || true fallback, but
wastes up to 2 minutes per restore cycle waiting on a condition that can
never be met at this point. Poll for the container process merely being
started instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-17 21:57:52 -05:00

..

restore-cronjob.yaml

Optimize vault-restore: don't wait on condition=Ready (verified working already)

2026-08-17 21:57:52 -05:00