From 804c8979e91331eaa6fcb2f606901033e2b35772 Mon Sep 17 00:00:00 2001 From: Teg79 Date: Tue, 17 Nov 2026 19:02:37 +0100 Subject: [PATCH] docs(cli): destroy and apply free the ledger entries of machines gone; teardown forgets stale ones Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA --- docs/reference/cli.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/docs/reference/cli.md b/docs/reference/cli.md index 96453f0..e47652d 100644 --- a/docs/reference/cli.md +++ b/docs/reference/cli.md @@ -361,7 +361,8 @@ usual times: [startup sequence](startup.md#urbex-apply-env); replacement names the attributes that force it and is never allowed. An application removed from `urbex.yaml` is a plain delete, which goes ahead only with `--delete-data`: `apply` names the LXCs and - volumes first, and deletes them. Then each named volume the LXC + volumes first, and deletes them, and frees their addresses in the + allocation ledger (`Freed the addresses of ...`). Then each named volume the LXC lacks becomes a mount point (`backup=1`), and a bigger `size` grows it; a smaller one is refused. An LXC that can't mount them at once is restarted, and the restart is said first. An application whose @@ -851,7 +852,8 @@ Removes an environment of the project, in this order: `environments///`, the environment's Terraform files and (now empty) state under `terraform/projects///`, its Ansible inventory under `ansible/projects///`, and its - entries in the allocation ledger. + entries in the allocation ledger: every machine its Terraform state + held, applications no longer in `urbex.yaml` included. The folder goes last on purpose: until the Stacks are gone, a push to `main` can still make the release Action update it, and removing it @@ -891,8 +893,13 @@ Destroys the platform `urbex bootstrap` created: the inverse of 1. Updates the GitOps repo from Gitea (if it still answers). 2. Refuses while any project environment exists - a folder under - `environments/` or an LXC in the allocation ledger - naming them: run - `urbex destroy ` in each project first. + `environments/` - naming them: run `urbex destroy ` in each + project first. Then an entry the allocation ledger still holds, left + by an older urbex, is forgotten if its machine is gone from Proxmox + (`Forgot stale entries of the allocation ledger ...`); if its machine + still exists, teardown stops and names it with its VMID: delete it in + the pool, or put its application back in `urbex.yaml` and run + `urbex destroy `. 3. Says what it destroys and what is lost: the base-service LXCs and their disks, so **every repository and image on Gitea** (project repos included - make sure they also live elsewhere), Komodo's, Keycloak's