8000 Enable start button on workspaces with forced updates · Issue #13002 · coder/coder · GitHub
[go: up one dir, main page]

Skip to content 8000
Enable start button on workspaces with forced updates #13002
Closed
@stirby

Description

@stirby

Problem Statement

Our template update policies requires workspaces to be on the latest version before starting their workspace.

Currently, when your workspace is out-of-date, we disable the start button and expect users to update manually:

start_greyed_out

This is especially frustrating when users want to start a workspace via connection, or from our Jetbrains extension. They have to open the UI and apply the update separately.

Solution Overview

We should enable the start button in the UI /gateway and have it "update and start".

The reason we decided to disable the button is likely to allow admins to start the workspace without the required update. This flow should stay the same with the addition of a heads-up saying the start didn't apply an update. I.E. admins will continue to manually update through the UI.


Edit:
We already corrected this in the VSCode extension:
coder/vscode-coder#233

Edit 2:
This is only a request for the UI, not extensions or ssh connections.

Metadata

Metadata

Assignees

Labels

customer-requestedFeatures requested by enterprise customers. Only humans may set this.siteArea: frontend dashboard

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0