docs: upcoming auto-stop behavior #8117
Conversation
| ```sh | ||
| coder templates create my-template --default-ttl 4h | ||
| ``` | ||
| - Auto-stop workspaces after 3 hours of inactivity. |
There was a problem hiding this comment.
nit: these clauses shouldn't end with periods since they're not complete sentences
|
|
||
| To control cost, specify a maximum time to live flag for a template in hours or | ||
| minutes. | ||
| By default, developers have unlimited workspace usage and can use any template version. Template policies allows you to: |
There was a problem hiding this comment.
Should add something about how developers have full control of their workspace schedules without policy. The policy is just the enforcement layer. It reads to me like the community edition doesn't have scheduling at all.
There was a problem hiding this comment.
Yeah, I agree. I will rephrase
|
|
||
| To control cost, specify a maximum time to live flag for a template in hours or | ||
| minutes. | ||
| By default, developers have unlimited workspace usage and can use any template version. Template policies allows you to: |
There was a problem hiding this comment.
Can't a developer use only the active version of a template? Only admins can create workspaces from any version.
There was a problem hiding this comment.
We plan on making the behavior configurable per-template.
There was a problem hiding this comment.
But restricting users to only use the active template is a good double-check if we do something like this
This is a draft PR as we align on the details of our new workspace auto-stop behavior.