seawall stack update

Move a stack's images to newer versions found by the update check, then deploy.

Usage

seawall stack update [OPTIONS] [STACK]

Changes the host

Without --yes it prints the plan and changes nothing.

Arguments

<STACK>

The stack, by Portainer name or directory

Options

--all

Every stack with a same-major update, one at a time

--container <CONTAINER>

Only this container's image

--to <TO>

An exact tag instead of the update check's candidate (needs a single image)

--major

Take the new major version where the update check found one

--data-backed-up

Each database has a tested backup of yours: no restore-tested dump from the last 24h needed

--allow-lint-errors

Update even if the change adds hardening errors

--rollback-on-failure

If the stack doesn't come up healthy, roll back without asking

--start-period

Add a start period to a health check whose first run comes 10s or more after a start, in this deploy, so it answers in seconds

--accept-grants

Accept the root grants it starts, writing each one's # seawall-lint: allow line, so later starts confirm with Enter

--yes

Carry out the plan (without it, this is a dry run)

--confirm <NAME>

The stack's name, to make a severe change without a terminal (--yes alone asks for it to be typed)

--plan <PIN>

The plan's pin: refused where the update changed since that plan

--wait

After a redeploy, wait out the 2-minute compare with before. Without it the facts timer runs it (SeawallDeployWorse)

Every command also takes the global options.

Examples

seawall stack update nextcloud
seawall stack update nextcloud --container nextcloud --to 31.0.9
seawall stack update --all --yes