GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||
GeezerVison is showing github.com — feat: allow template version selection for workspace builds by dylanhuff-at-coder · Pull Request #30199 · coder/coder Conversation
Contributor
Add named template version selection to Classic stop builds retain previous parameter values omitted by the selected stop version, so a later start can reuse them across separate commands or an interrupted update. Declared parameters still follow normal validation, and start builds still discard removed parameters. Update now returns an error and retry guidance when a start apply fails after stopping, including unflagged updates that previously returned success. Closes #29100
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsAll reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
dylanhuff-at-coder
marked this pull request as ready for review
|
There was an error while loading. Please reload this page.
Documentation CheckUpdates Needed
Automated review via Coder Agents |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
- Preserve omitted classic parameters on delete builds, not just stop. - Stop update from starting a stopped workspace when only --stop-template-version is passed. On a cleanly stopped workspace with other update work, warn and ignore the flag. Otherwise error, since there is nothing for update to stop. - Name the actual target version in the update confirmation prompt. - Quote 'coder start' in update retry guidance. - Share the template version name lookup with coder create. - Document the new flags in the workspace management guide.
There was an error while loading. Please reload this page.
Docs previewCheck off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Added a short section on the new flags to the workspace management guide |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Some docs styling nits, but otherwise, docs LGTM!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Nick Vigilante <[email protected]>
Co-authored-by: Nick Vigilante <[email protected]>
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
CLI: allow specifying a template version for stop/start builds and both legs ofcoder update
There was an error while loading. Please reload this page.