Skip to main content

Confirm a started stack sees its data

POST 
/migrate/containers/:name/confirm

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/migrate/containers/{name}/confirm"

Records that the user read the data check and the started stack sees its data, which offers the next stack. Refused with 409 container_not_started for a stack that was not started, 409 data_check_required until checkMigrationContainer has run since the latest start, 409 data_check_failed when that check found a path that is missing, empty or unreadable unless acceptFailedCheck is true (a container whose data directory is meant to be empty), and 409 container_not_running when none of the stack's containers is running (stop the container instead, to go on without it). Confirming a confirmed stack changes nothing. 409 parity_not_initialized and 404 migrated_stack_not_found as startMigrationContainer does.

Request​

Responses​

The stack, confirmed.