homelab/compose-files
0
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

vaultwarden: retry #6 -- re-trigger after fixing invalid 3DPRINT_DB_PASSWORD env var name
ci/woodpecker/push/deploy Pipeline failed
Details

Browse Source
This commit is contained in:
admin
2026-07-27 12:13:05 -07:00
parent 332708ad41
commit 1a1068a154
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
vaultwarden/vaultwarden.env
+4 -4
View File
@@ -1,7 +1,7 @@
# Vaultwarden - Pattern B env (folder-mode); ADMIN_TOKEN/DATABASE_URL are Docker secrets # 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' # 2026-07: DATABASE_URL secret rotated to point at 'postgresql' alias instead of 'db'
# as part of PostgreSQL HA migration prep (ADR-0001). # as part of PostgreSQL HA migration prep (ADR-0001).
# Retry #5: repo switched back to public, secret injection confirmed working # Retry #6: found and fixed the actual root cause -- 3DPRINT_DB_PASSWORD env var alias
# (SSH_KEY=516B, SWARM_MANAGER_IP=12B). All known pipeline bugs fixed. This is # started with a digit (invalid per POSIX), likely poisoning the whole environment
# the real end-to-end test -- should provision vaultwarden_database_url_v2, # block for provision-secrets and causing SWARM_MANAGER_IP to read empty in that
# deploy the stack, and verify the task comes back healthy. # step specifically. Renamed to PRINT3D_DB_PASSWORD. This should be the real fix.