vaultwarden: retry #6 -- re-trigger after fixing invalid 3DPRINT_DB_PASSWORD env var name
ci/woodpecker/push/deploy Pipeline failed
ci/woodpecker/push/deploy Pipeline failed
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
# Vaultwarden - Pattern B env (folder-mode); ADMIN_TOKEN/DATABASE_URL are Docker secrets
|
||||
# 2026-07: DATABASE_URL secret rotated to point at 'postgresql' alias instead of 'db'
|
||||
# as part of PostgreSQL HA migration prep (ADR-0001).
|
||||
# Retry #5: repo switched back to public, secret injection confirmed working
|
||||
# (SSH_KEY=516B, SWARM_MANAGER_IP=12B). All known pipeline bugs fixed. This is
|
||||
# the real end-to-end test -- should provision vaultwarden_database_url_v2,
|
||||
# deploy the stack, and verify the task comes back healthy.
|
||||
# Retry #6: found and fixed the actual root cause -- 3DPRINT_DB_PASSWORD env var alias
|
||||
# started with a digit (invalid per POSIX), likely poisoning the whole environment
|
||||
# block for provision-secrets and causing SWARM_MANAGER_IP to read empty in that
|
||||
# step specifically. Renamed to PRINT3D_DB_PASSWORD. This should be the real fix.
|
||||
|
||||
Reference in New Issue
Block a user