Skip to content

Add owner-authenticated cancellation for one app registration #63

Closed as not planned

Description

@j0sh

Superseded by Node-owned draining in #23

The revised boundary is tracked in #23: an accepted heartbeat that removes an app begins a bounded drain owned and enforced by Node. Node stops new admission/discovery, preserves existing work until completion or the first deadline, and performs normal session/payment/request/proxy/channel teardown at expiry. Runtime observes the result through heartbeats and stages workload replacement.

The original purpose of this ticket was for Runtime to enforce its own drain timer and then call an owner-authenticated POST /runners/{runner_id}/apps/{app_id}/cancel without session tokens. That operation is no longer required for the maintenance/upgrade flow: Node already owns the sessions it must end. No separate immediate force-cancel use case has been established for this ticket.

Disposition of the reviewed implementation

Closing as superseded / not planned. Integrated acceptance remains in naap-ops #118.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions