Related#813

In v1, we have customers that wanted to shut down all workspaces in an organization on a period while simultaneously giving their developers control to suit their working patterns and time zone.

The problem with developer controlled auto stop is they're not the ones incentivized to reduce costs.

Solution

The cleanest solution I could think of is we allow the ability to set an auto-start at thetemplate level in addition to the workspace level. That auto-stop can be overridden by the workspace, but only by schedules that have the same interval or less. For example, if a daily auto-stop is set in the template, a daily one must be set by the user.

Auto start policy is flipped, the template interval serves as the floor instead of the ceiling.

A caveat with this approach is UX complexity.

For example, if I set a template cron auto start of 9am CST Mon to Fri, and then a user configures 9AM GMT Tues to Sun (one extra day), we need a really clear error, because it's an easy mistake to make.

Org-level auto-start

We don't implement this. For one, it's added complexity. For two, the templates describe the resource costs, they should also describe the cost management. This is consistent withmy proposed quota system.

cc@johnstcn

Acceptance Criteria

• [/] Template: setmax_ttl andmin_autostart_duration
• [/] Workspace:ttl andautostart_schedule constrained by template
• [/] Template: updatemax_ttl andmin_autostart_duration