Deployment lifecycle
Keep the original idempotency key after a timeout or disconnect. Inspect the durable operation and its events before retrying; a new key represents a new mutation intent.
Recover a failed worker or replace a deployment
InferCrane has no imperativerestart command. If an owned provider resource disappears, the
reconciler uses the persisted replica intent and provider identity to observe, adopt, or recreate it;
closing the CLI is not a reason to submit another deployment. Follow the same durable work:
X-Request-Id response header as REQUEST_ID. Provider-native systems may not expose a
physical replica identity; the inspection leaves that field unavailable instead of guessing.
Decide whether provider drift is recoverable
Compare the persisted provider identity, intent digest, ownership tags, revision, and replica ordinal frominspect with a read-only provider inventory before allowing reconciliation:
An empty
infercrane orphans result is not enough when provider credentials cannot see the full
account or namespace. Manual intervention ends only when one authoritative provider identity can be
matched to one durable replica intent - or absence is proven by the owning provider boundary.
Delete first withdraws desired routing, then drains and removes external resources. Restarting midway resumes cleanup. Completion requires provider absence, removed targets and replicas, and a deployment tombstone. Operators should still verify provider inventory after paid acceptance tests.
Cancelling a deployment’s first deploy while it runs uses the same cleanup. It removes any capacity
the deploy started and finishes with the same tombstone, so the name is released exactly as after a
delete. A deploy cancelled before any work started leaves the deployment in place; delete it to
release the name.
Delete without losing recovery state
Preview the exact effect before mutation. Confirm explicitly, give the request a stable retry key, and wait for the durable provider cleanup operation:--yes, verify the plan names only the intended deployment, revisions, targets, replicas,
and provider identities. Inspect every endpoint binding that references the deployment and decide
whether it needs a replacement plan. Confirm ownership mode: observe-only and traffic-managed
adoptions do not grant lifecycle deletion of the upstream; lifecycle-managed capacity must have
matching durable provider ownership. Also check external fallback, async jobs, active streams, and
retained release evidence required by your policy. InferCrane will not guess how an application
should replace a deleted endpoint dependency.
The endpoint InferCrane created for the deployment (its own name, or the endpoint_name it
published) is deleted together with the deployment, because nothing else can serve it. If you bound
another backend to that endpoint, InferCrane keeps it and leaves the replacement plan to you.
Endpoints you created and bound yourself are never deleted with a deployment.
If the terminal disconnects, do not submit a new intent with a new key. Reattach with the operation
ID returned by delete, or inspect the persisted deployment events. After completion, verify both
InferCrane state and the provider boundary:
--keep-resources while cleanup is unresolved unless you intentionally accept external ownership.