fix: force-pull images on install and fix provisioning test assertions
All checks were successful
CI / build (push) Successful in 1m11s
CI / docker (push) Successful in 47s

Installers now use `--pull always --force-recreate` on `docker compose up`
to ensure fresh images are used on every install/reinstall, preventing
stale containers from missing schema changes like db_password.

Fix VendorTenantServiceTest to expect two repository saves in provisioning
tests (one for dbPassword, one for final status).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
hsiegeln
2026-04-15 08:50:40 +02:00
parent 6eb848f353
commit 15306dddc0
3 changed files with 5 additions and 4 deletions

View File

@@ -1119,7 +1119,7 @@ function Invoke-ComposeUp {
$c = $script:cfg
Log-Info 'Starting Cameleer platform...'
Push-Location $c.InstallDir
try { docker compose -p $c.ComposeProject up -d }
try { docker compose -p $c.ComposeProject up -d --pull always --force-recreate }
finally { Pop-Location }
Log-Info 'Containers started -- verifying health next.'
}

View File

@@ -1144,7 +1144,7 @@ docker_compose_pull() {
docker_compose_up() {
log_info "Starting Cameleer SaaS platform..."
(cd "$INSTALL_DIR" && docker compose -p "$COMPOSE_PROJECT" up -d) || true
(cd "$INSTALL_DIR" && docker compose -p "$COMPOSE_PROJECT" up -d --pull always --force-recreate) || true
log_info "Containers started — verifying health next."
}