- Notifications
You must be signed in to change notification settings - Fork948
feat: add workspace_apps configuration to control apps in workspace table#18922
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Updated the button labels on the /workspaces page to clearly indicate that VS Code opens in the browser, matching the UI mockup provided.
…pace table- Added workspace_apps field to terraform coder_agent resource- Updated proto definition to include workspace_apps- Modified frontend WorkspaceApps component to respect configured apps- Allows specifying which apps (built-in and custom) appear in the workspace table- Maximum of 4 apps displayed, in the order specified
- Add database migration for workspace_apps column- Update SQL queries to include workspace_apps- Update provisioner server to pass workspace_apps from terraform- Still needs: database code regeneration and API updates
Add workspace_apps configuration to control which apps appear in workspace table:- Add database migration for workspace_apps column- Update WorkspaceAgent struct to include workspace_apps field- Update SQL queries to handle workspace_apps- Add comprehensive tests for the new functionality- Add documentation with examplesThis allows administrators to configure via Terraform which appsappear as action buttons in the workspace table while maintainingbackward compatibility.
0c281d9
toeb77a5e
CompareThis ensures the generated database code includes the workspace_apps fieldneeded for the feature to compile properly.
This can be controlled with |
johnstcn left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Is the intention here to allow full customization of the apps shown in the workspace list as opposed to the workspace details? Having a different ordering on the list as opposed to the details page seems potentially confusing.
Instead of adding yet another field on our provider, an alternative solution could be to simply include the first fourcoder_app
instances based on theorder
field and what is set indisplay_apps
. I'd suggestdisplay_apps
taking priority and then 'filling in' the remainder with the top Ncoder_apps
based onorder
(up to max 4 apps).
EDIT: this appears to be the current logic. We first prioritize the 'built-in apps' and then fill in the remaining 'slots' with any healthy non-hidden user apps.
This PR adds the ability to configure which apps appear in the workspace table on the /workspaces page via terraform.
Changes
workspace_apps
field to thecoder_agent
terraform resourceUsage Example
Implementation Notes
TODO
Requested by@jacqueline in Slack.