Title: Template constraint for workspace scheduling · Issue #1433 · coder/coder · GitHub
Open Graph Title: Template constraint for workspace scheduling · Issue #1433 · coder/coder
X Title: Template constraint for workspace scheduling · Issue #1433 · coder/coder
Description: 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 co...
Open Graph Description: 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 ...
X Description: 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 ...
Opengraph URL: https://github.com/coder/coder/issues/1433
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Template constraint for workspace scheduling","articleBody":"Related https://github.com/coder/coder/issues/813\r\n\r\nIn 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. \r\n\r\nThe problem with developer controlled auto stop is they're not the ones incentivized to reduce costs.\r\n\r\n## Solution\r\n\r\nThe cleanest solution I could think of is we allow the ability to set an auto-start at the _template_ 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.\r\n\r\nAuto start policy is flipped, the template interval serves as the floor instead of the ceiling.\r\n\r\nA caveat with this approach is UX complexity.\r\n\r\nFor 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. \r\n\r\n## Org-level auto-start\r\nWe 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 with [my proposed quota system.](https://www.notion.so/coderhq/Quotas-v2-c03453d1aba64e7d801c2cd5d1b11049)\r\n\r\n---\r\n\r\ncc @johnstcn \r\n\r\n\r\n## Acceptance Criteria\r\n\r\n- [/] Template: set `max_ttl` and `min_autostart_duration`\r\n- [/] Workspace: `ttl` and `autostart_schedule` constrained by template\r\n- [/] Template: update `max_ttl` and `min_autostart_duration`","author":{"url":"https://github.com/ammario","@type":"Person","name":"ammario"},"datePublished":"2022-05-13T17:32:42Z","url":"https://github.com/coder/coder/issues/1433"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:a3fde3a8-f65d-197d-8026-144b90b782d3 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8A48:1CEA6F:1CCD873:25EB178:6B0154F7 |
| html-safe-nonce | 705519d925681752d6be95745e9befdd1303ae3c89232faa72707ee105890afd |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4QTQ4OjFDRUE2RjoxQ0NEODczOjI1RUIxNzg6NkIwMTU0RjciLCJ2aXNpdG9yX2lkIjoiMjg1MDM0MTQ2MjgwNDA5MjE1MSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 66976523e1ea98de4b03b21bc5cb8164fcef9fcaf421e58816a95d3bea43dd5a |
| hovercard-subject-tag | issue:1235506347 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/coder/coder/1433/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c1c209a0cbee34014cf1e1b0d52aecd406306c8b137800c10dc6e6367587e800/coder/coder/issues/1433 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c1c209a0cbee34014cf1e1b0d52aecd406306c8b137800c10dc6e6367587e800/coder/coder/issues/1433 |
| og:image:alt | 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 ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | ammario |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/coder/coder git https://github.com/coder/coder.git |
| octolytics-dimension-user_id | 95932066 |
| octolytics-dimension-user_login | coder |
| octolytics-dimension-repository_id | 440752086 |
| octolytics-dimension-repository_nwo | coder/coder |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 440752086 |
| octolytics-dimension-repository_network_root_nwo | coder/coder |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width