Thanks to visit codestin.com
Credit goes to github.com

Skip to content

bug: coder update <workspace> --always-prompt does not start the workspace #6336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ericpaulsen opened this issue Feb 24, 2023 · 1 comment · Fixed by #6437
Closed

bug: coder update <workspace> --always-prompt does not start the workspace #6336

ericpaulsen opened this issue Feb 24, 2023 · 1 comment · Fixed by #6437
Assignees
Labels
s2 Broken use cases or features (with a workaround). Only humans may set this.

Comments

@ericpaulsen
Copy link
Member

ericpaulsen commented Feb 24, 2023

version v0.17.4-devel+16363fd1

running coder update <workspace> --always-prompt correctly prompts me to reset my terraform variables and re-initializes terraform.

however, navigating back to the UI shows the workspace still in a Stopped state. note that the prior state was an auto-shutoff by Coder:

Screenshot 2023-02-23 at 6 07 27 PM

this code suggests that the workspace transition leverages the state of the latest build.

@bpmct bpmct added the s2 Broken use cases or features (with a workaround). Only humans may set this. label Feb 24, 2023
@Emyrk
Copy link
Member

Emyrk commented Mar 3, 2023

Yea, this should probably start the workspace. I'll fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s2 Broken use cases or features (with a workaround). Only humans may set this.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants