* fix: Use WebSockets to stream workspace build logs
This was using a streaming HTTP request before, which didn't work
on my version of Chrome. This method seemed less reliable and standard
than a WebSocket, so figured switching would be best.
* Update site/src/xServices/workspaceBuild/workspaceBuildXService.ts
Co-authored-by: Abhineet Jain <AbhineetJain@users.noreply.github.com>
* Update site/src/pages/WorkspaceBuildPage/WorkspaceBuildPage.test.tsx
Co-authored-by: Abhineet Jain <AbhineetJain@users.noreply.github.com>
* Update site/src/api/api.ts
Co-authored-by: Abhineet Jain <AbhineetJain@users.noreply.github.com>
* Remove unused prop
Co-authored-by: Abhineet Jain <AbhineetJain@users.noreply.github.com>
Since the footer is included in every page, we should try extra
hard to use little vertical space.
Also, I add an icon to the version text for balance.
* add reason field for workspace build
* add the reason field to FE via API
* update BuildReasonMember to BuildReasonInitiator
* add unit tests
* add more unit tests
* add error for unknown transition
* fix lint
* add documentation
* fix unit tests
* fix generated types
* remove nested transaction
* rename migration file
* add ability to activate users
resolves#2254
* added test
* PR feedback
* guarding against null validation_contains field
* fixing type for ParameterSchema
resolves#2161
* added report link to footer
resolves#1885
* added test
* Footer story
* fix broken test
* WIP: feat: Update templates also updates parameters
* Insert params for template version update
* Working implementation of inherited params
* Add "--always-prompt" flag and logging info
* add ability to activate users
resolves#2254
* added test
* PR feedback
* guarding against null validation_contains field
* fixing type for ParameterSchema
resolves#2161
- When a workspace is deleted the user is nudged
to create a new workspace. The page to which they
are routed 404s. This PR simply routes them to the
/templates page where they can pick a template for their
new workspace.
This commit makes the following changes:
- Partially reverts the changes of feat: update workspace deadline when workspace ttl updated #2165, making the deadline of a running workspace build independant of TTL, once started.
- CLI: updating a workspace TTL no longer updates the deadline of the workspace.
- UI: updating a workspace TTL no longer updates the deadline of the workspace.
- Drive-by: API: When creating a workspace, default TTL to min(12 hours, template max_ttl) if not instructed otherwise.
- Drive-by: CLI: list: measure workspace extension correctly (+X in last column) from the time the provisioner job was completed
- Drive-by: WorkspaceSchedule: show timezone of schedule if it is set, defaulting to dayjs guess otherwise.
- Drive-by: WorkspaceScheduleForm: fixed an issue where deleting the "TTL" value in the form would show the text "Your workspace will shut down a few seconds after start".
* feat: add support for template in workspace filter
* feat: Implement workspace search filter to support names
* Use new query param parser for pagination fields
* Remove excessive calls, use filters on a single query
Co-authored-by: Garrett <garrett@coder.com>
* design commit
* add owner_id to templates table
* add owner information in apis and ui
* update minWidth for statItem
* rename owner to created_by
* missing refactor to created_by
* handle errors in fetching created_by names
Summary:
Various time displays weren't quite right.
Details:
- Display date (not just time) of upcoming workspace stop in workspace
page
- Fix ttlShutdownAt for various cases + tests
- manual to non-manual
- unchanged/unmodified
- isBefore --> isSameOrBefore
- use the delta (off by _ error)
- pluralize units in dayjs.add
Jon Ayers