Skip to content

fix: prompt instead of defaulting when a previous parameter option is removed - #30797

Open
aslilac wants to merge 1 commit into
mainfrom
lilac/cli-stale-parameter-prompt
Open

aslilac wants to merge 1 commit into
mainfrom
lilac/cli-stale-parameter-prompt

Conversation

@aslilac

@aslilac aslilac commented Oct 14, 2026

Copy link
Copy Markdown
Member

Follow-up to #30660 for CLIENT-697.

With --use-parameter-defaults, which coder ssh auto-start always sets, a mutable parameter whose previous value was removed from the new template version was silently replaced with the template default. Switching a value like a region that way can destroy a workspace's resources.

The CLI now prompts for a new value in that case when stdin is a terminal, and fails with a message pointing to coder update when it is not (including ssh workspace.coder, which runs coder ssh --stdio). New parameters keep using their defaults as before.

Decisions
  • The check lives in the parameter resolver, so explicit --use-parameter-defaults on start/update/restart behaves the same as ssh auto-start. Scripts relying on the fallback will now fail instead of moving users to the default.
  • coder update and coder restart still stop a running workspace before resolving parameters (existing behavior), so a non-interactive run leaves it stopped with the error.

Generated by Coder Agents.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant