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
--allEvery 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)
--majorTake the new major version where the update check found one
--data-backed-upEach database has a tested backup of yours: no restore-tested dump from the last 24h needed
--allow-lint-errorsUpdate even if the change adds hardening errors
--rollback-on-failureIf the stack doesn't come up healthy, roll back without asking
--start-periodAdd 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-grantsAccept the root grants it starts, writing each one's
# seawall-lint: allowline, so later starts confirm with Enter--yesCarry out the plan (without it, this is a dry run)
--confirm <NAME>The stack's name, to make a severe change without a terminal (
--yesalone asks for it to be typed)--plan <PIN>The plan's pin: refused where the update changed since that plan
--waitAfter a redeploy, wait out the 2-minute compare with before. Without it the facts timer runs it (
SeawallDeployWorse)
Examples
seawall stack update nextcloud
seawall stack update nextcloud --container nextcloud --to 31.0.9
seawall stack update --all --yes