Allow interrupting/cancelling an in-progress deployment #406

Open
opened 2026-08-04 11:06:07 +00:00 by vkobel · 0 comments
vkobel commented 2026-08-04 11:06:07 +00:00 (Migrated from codeberg.org)

After running git push caution main, the deploy command blocks until the deployment finishes. There is currently no reliable way to stop it early.

caution apps destroy appears like the obvious escape hatch, but it does not successfully cancel an active deployment.

We should support explicitly cancelling a deployment while it is queued, building, or starting up—ideally from another terminal by app/deployment ID—and return a clear final cancelled state.

Acceptance criteria:

  • a user can cancel an in-progress deployment without waiting for it to finish
  • cancellation stops outstanding build/provisioning work and releases resources where possible
  • the CLI reports whether cancellation succeeded, was already complete, or cannot be performed
  • repeated cancellation requests are safe/idempotent
  • caution apps destroy either reliably handles this case or directs users to the dedicated cancellation command
After running git push caution main, the deploy command blocks until the deployment finishes. There is currently no reliable way to stop it early. caution apps destroy appears like the obvious escape hatch, but it does not successfully cancel an active deployment. We should support explicitly cancelling a deployment while it is queued, building, or starting up—ideally from another terminal by app/deployment ID—and return a clear final cancelled state. Acceptance criteria: - a user can cancel an in-progress deployment without waiting for it to finish - cancellation stops outstanding build/provisioning work and releases resources where possible - the CLI reports whether cancellation succeeded, was already complete, or cannot be performed - repeated cancellation requests are safe/idempotent - caution apps destroy either reliably handles this case or directs users to the dedicated cancellation command
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
public/platform#406
No description provided.