8000 chore: add prebuild docs by dannykopping · Pull Request #17580 · coder/coder · GitHub
[go: up one dir, main page]

Skip to content

chore: add prebuild docs #17580

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

Merged
merged 22 commits into from
May 9, 2025
Merged
Changes from 1 commit
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
md/copy
  • Loading branch information
EdwardAngert committed May 7, 2025
commit 596d7a0f489ec79c1332cc5a4194ebc03fca07c5
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Prebuilt workspaces are tightly integrated with [workspace presets](./parameters

## Enable prebuilt workspaces for template presets

In your template, add a `prebuilds` block within a `coder_workspace_preset` definition to identify how many prebuilt
In your template, add a `prebuilds` block within a `coder_workspace_preset` definition to identify the number of prebuilt
instances your Coder deployment should maintain:

```hcl
Expand Down Expand Up @@ -71,7 +71,7 @@ Prebuilt workspaces follow a specific lifecycle from creation through eligibilit
1. The agent starts its bootstrap procedures and completes its startup scripts.
1. The agent reports `ready` status.

Only once the agent reports `ready` is the prebuilt workspace considered eligible.
After the agent reports `ready`, the prebuilt workspace considered eligible to be claimed.

Prebuilt workspaces that fail during provisioning are retried with a backoff to prevent transient failures.

Expand All @@ -84,12 +84,11 @@ Prebuilt workspaces follow a specific lifecycle from creation through eligibilit
[`coder_workspace_owner`](https://registry.terraform.io/providers/coder/coder/latest/docs/data-sources/workspace_owner)
datasources (see [Preventing resource replacement](#preventing-resource-replacement) for further considerations).

The process is transparent to the developer - they simply see a workspace ready faster than normal.
The process is invisible to the developer - their workspace is ready faster than usual.

You can view available prebuilt workspaces in the **Workspaces** view in the Coder dashboard:

![A prebuilt workspace in the dashboard](../../../images/admin/templates/extend-templates/prebuilt/prebuilt-workspaces.png)

_Note the search term `owner:prebuilds`._

### Template updates and the prebuilt workspace lifecycle
Expand Down
Loading
0