fix: force-pull images on install and fix provisioning test assertions
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:
@@ -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.'
|
||||
}
|
||||
|
||||
@@ -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."
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user