Skip to main content

Update several containers

POST 
/apps/updates

Required role: admin. Only an account or token with the admin role can call this operation.

Example request
curl --request POST \
  --header "Authorization: Bearer $HOSERVA_TOKEN" \
  --header "Content-Type: application/json" \
  --data @body.json \
  "https://$HOSERVA_HOST:8008/api/v1/apps/updates"

Queues one container_update job (service class) that updates the named containers one after another, each as updateApp does: an appdata snapshot first when its appdata sits on the cache disk, then the update, keeping the image it ran before for a revert. One container's failure does not stop the others; the job fails, naming each, once they have all been tried, and a container that failed is left on its previous image. With no containers, the targets are the containers the last update check found a newer image for, minus those that opted out of bulk updates (setAppUpdatePolicy); those come back in skipped. Naming a container updates it whether or not it opted out. When there is nothing to update no job is queued and job is absent. Refused with 409 array_stopped while the array is stopped (maintenance mode) or its storage is not ready, and with 503 array_state_unknown if the array's state cannot be read; no job is queued. An unknown container is 404 and queues nothing.

Request​

Responses​

The queued job and what was left out.