Auto power-on after resize and interactive disk resize option

[gwpl]

Summary

AI Agent with Greg: We got caught with our droplet's pants down — resized it, went to SSH in, and found it sitting there powered off like a server that took an unauthorized coffee break. ☕🔌 Meanwhile, the disk resize nearly ate our ability to scale back down. Two papercuts, one patch.

• Auto power-on after resize — DigitalOcean leaves droplets powered off after resize (no API flag exists to change this). The command now automatically powers the droplet back on with progress polling, instead of leaving users to discover a cold droplet and manually run dropkit on.

• Interactive disk resize option — --disk/--no-disk is now a tri-state (True/False/None). When neither flag is passed and the new size has a different disk allocation, the user gets an interactive prompt asking whether to include disk in the resize. The prompt warns that disk resize is permanent and defaults to "no" to protect reversibility. Power users can still pass --disk or --no-disk explicitly to skip the prompt.

Use case: temporary scale-up

# Scale up for a build — interactive prompt defaults to skipping disk
$ dropkit resize my-box --size s-4vcpu-8gb
...
⚠ Disk resize is PERMANENT and cannot be undone.
Skipping disk resize keeps the option to downsize later.
Resize disk too? [yes/no] (no): no
...
✓ Resize completed successfully

Powering on droplet...
✓ Power on action started (ID: 3105287233)
Waiting for droplet to power on...
✓ Droplet powered on successfully

# Later, scale back down — works because disk was never resized
$ dropkit resize my-box --size s-1vcpu-1gb

# Or skip the prompt entirely with explicit flags:
$ dropkit resize my-box --size s-4vcpu-8gb --no-disk
$ dropkit resize my-box --size s-4vcpu-8gb --disk

Technical notes

• Interactive prompt only appears when --disk/--no-disk is not specified AND the new size has a different disk allocation
• Power-on uses the same pattern as dropkit on: 120s timeout, action ID validation, console.status() spinner
• If the power-on action ID can't be obtained, falls back to a warning with manual instructions
• Confirmed via DigitalOcean API spec: no power_on_after_resize parameter exists — two sequential API calls (resize → power_on) is the only path

Test plan

• uv run ruff check dropkit/main.py — passed
• uv run ruff format --check dropkit/main.py — passed
• prek run — all checks passed
• Manual test: resize with no flag (interactive prompt appears)
• Manual test: resize with --disk (no prompt, disk resized)
• Manual test: resize with --no-disk (no prompt, disk skipped)

🤖 Generated with Claude Code

[ret2libc]

Can't you use dropkit resize --no-disk test-resize instead of adding a new option? This will resize the droplet without resizing the disk.

[gwpl]

Greg:

TL;DR — Yes, --no-disk works technically. This PR is solving a TUI UX / cognitive overhead problem, consistent with dropkit's purpose of making things easier for users than using doctl directly.

Let me unpack my thinking here :)

• Not all dropkit users are DigitalOcean power users — and that's kind of the point of dropkit
• The fact that you must not resize disk in order to preserve the ability to downsize later is non-obvious. It's a DigitalOcean implementation detail that catches people off guard
• The existing --no-disk flag works, but it requires users to already know this gotcha before they hit Enter

From a TUI UX perspective, nodisk as an inline option is the most forgiving design — it surfaces the information at decision time, right when the user sees "Disk resize is PERMANENT." Compare the two experiences:

With nodisk option: User sees the warning, sees the escape hatch, picks it. Done in one flow.

Without: User sees the warning, panics, cancels, has to remember --no-disk, re-runs the command. Extra cognitive load every time.

That said, I totally get that "where to draw the line on hand-holding in the CLI" is a judgment call. If you'd prefer to keep it flag-only, an alternative would be a more explicit warning like: "⚠ Disk resize is permanent — you will not be able to downsize later. Re-run with --no-disk to skip disk resize." Worse UX in my opinion (why make the user restart when we can handle it inline?), but not the end of the world either.

Ultimately my concern is about cognitive-overloaded peers who picked dropkit specifically to reduce the overhead of working with doctl directly — making them memorize flags for every footgun somewhat defeats that purpose 😄

[DarkaMaul]

Just my 2 cents here - maybe I would instead display a warning here to educate instead of the new option nodisk.
If I'm not a power user, then I don't know what nodisk means anyway.

Ok - I read the code, and the warning is already present there...

[ret2libc]

Thanks a lot for the patience and for addressing all the comments!