Skip to content

e2e-verify tracebloc delete offboard teardown against a throwaway k3d cluster #140

Description

@saadqbal

Follow-up to #139 / #136. Offboarding — the top-level tracebloc delete (deprovision/revoke + helm uninstall + k3d cluster delete + clear the active-client pointer) — is currently unit-tested only (fake runner in internal/nodeboot; logic in internal/cli/delete.go). CI e2e.yml covers data ingest, not teardown. Before the offboarding surface promotes to prod, run it end-to-end on a throwaway k3d box:

  • create a client, confirm the release + cluster exist;
  • tracebloc delete --yes;
  • confirm: the backend credential is revoked (POST /edge-device/<id>/revoke/ — not a hard DELETE; the client row is kept as history per §7.10), the Helm release is uninstalled, the k3d cluster is deleted, ~/.tracebloc is wiped (or kept under --keep-data with the pointer cleared), and a foreign tb alias / system tooling is left untouched (the fix(cli): delete only removes tb when it is tracebloc's own alias #171 guard).

Do NOT run against the shared reference box (18.196.47.80) — it would destroy the live tracebloc-amazon client.

Rescoped 2026-07-07: client delete → the shipped top-level tracebloc delete; the teardown surface landed in #160/#165/#168/#169/#171 (now Ready for staging), so this is the pre-prod e2e gate.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions