feat: extend workspace build reasons to track connection types #18827
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces new build reason values to identify what type of connection triggered a workspace build, helping to troubleshoot workspace-related issues.
Database Migration
Added migration 000349_extend_workspace_build_reason.up.sql that extends the build_reason enum with new values:
Implementation
The build reason is specified through the API when creating new workspace builds:
dashboard
when users start workspaces via the web interfacestart
command: Sets reason tocli
when workspaces are started via the command linessh
command: Sets reason to ssh_connection when workspaces are started due to SSH connectionsvscode_connection
by the VS Code extension through CLI hidden flagjetbrains_connection
when the user agent contains "Coder Toolbox" or "Coder Gateway" (set by JetBrains extensions)