mirror of
https://github.com/trailofbits/dropkit
synced 2026-06-21 14:11:54 +00:00
44cb274bcc
* Show actual disk size instead of size spec in resize command After a --no-disk resize, `dropkit resize` showed the size spec's disk (e.g. 80 GB for s-2vcpu-4gb) instead of the droplet's actual disk (25 GB). This is confusing for users planning temporary scale-ups — they need to see their real disk to know if they can scale back down. Read disk from `droplet["disk"]` (actual allocation) instead of `droplet["size"]["disk"]` (what the size tier offers). When the two differ, show an inline hint: "25 GB (size spec: 80 GB, disk was not resized)" so the situation is immediately clear. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Use actual droplet vcpus and memory, not just disk Read all three resource fields from the droplet object directly (droplet["vcpus"], droplet["memory"], droplet["disk"]) instead of from the size spec (droplet["size"]["vcpus"], etc.). After a --no-disk resize these can diverge — the size spec reflects the new tier while the droplet retains its original resources. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>