Skip to content

feat: extend workspace build reasons to track connection types #18827

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

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

kacpersaw
Copy link
Contributor

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:

dashboard, cli, ssh_connection, vscode_connection, jetbrains_connection

Implementation

The build reason is specified through the API when creating new workspace builds:

  • Dashboard: Automatically sets reason to dashboard when users start workspaces via the web interface
  • CLI start command: Sets reason to cli when workspaces are started via the command line
  • CLI ssh command: Sets reason to ssh_connection when workspaces are started due to SSH connections
  • VS Code connections: Will be set to vscode_connection by the VS Code extension through CLI hidden flag
  • JetBrains connections: Automatically set to jetbrains_connection when the user agent contains "Coder Toolbox" or "Coder Gateway" (set by JetBrains extensions)

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