Skip to content

Move template schedule controls into enterprise #3304

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.

Sign up for GitHub

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

Jump to bottom
Closed
Tracked by #3182
ammario opened this issue Jul 29, 2022 · 8 comments · Fixed by #4843
Closed
Tracked by #3182

Move template schedule controls into enterprise #3304

ammario opened this issue Jul 29, 2022 · 8 comments · Fixed by #4843
Assignees
@f0ssel
Labels
enterprise Enterprise-license / premium functionality
Milestone
EE

Comments

@ammario
Copy link
Member

ammario commented Jul 29, 2022 •
edited
Loading

Problem Statement

DevOps, Admins, and leaders prioritize cost control and reducing infrastructure spending. They need control to mandate auto-stop policies to help prevent overspend on cloud resources.

Users turn off their workspace out of goodwill, and goodwill disappears as the deployment grows and the users become more alienated from the person holding the budget.

Definition of Done

These template flags are used for setting default workspace controls and should be moved behind Enterprise licensing.
The specific flags are:
@ammario ammario added the enterprise Enterprise-license / premium functionality label Jul 29, 2022
@ammario ammario mentioned this issue Jul 29, 2022
Closed
25 tasks
@tjcran
Copy link

tjcran commented Jul 29, 2022

huge agree

@sharkymark

This comment was marked as resolved.

Sign in to view
@ammario ammario mentioned this issue Jul 31, 2022
Closed
@tjcran
Copy link

tjcran commented Aug 12, 2022

@spikecurtis @presleyp if we need a smaller test target for licensing that may be finished before Audit Logging, this is a good candidate.

@misskniss
Copy link

Need some additional information here about how this will behave as part of a licensed feature: does it show up as a toggle on the licensing page? etc.

@misskniss
Copy link

We will hold on this until after we bring in audit logging.

@ammario
Copy link
Member Author

ammario commented Aug 16, 2022

Need some additional information here about how this will behave as part of a licensed feature: does it show up as a toggle on the licensing page? etc.

This should appear as a toggle on the Template page, and anyone with edit access to the template may edit the schedule controls.

@tjcran
Copy link

tjcran commented Aug 16, 2022

Need some additional information here about how this will behave as part of a licensed feature: does it show up as a toggle on the licensing page? etc.

This should appear as a toggle on the Template page, and anyone with edit access to the template may edit the schedule controls.

I think the question was asking on how the feature should be enabled/disabled. e.g. Audit Logging will have an admin toggle to enable/disable audit logging as a feature.

I don't think that is necessary for this feature... and the feature itself could have controls on the template page as Ammar suggested.

@ammario
Copy link
Member Author

ammario commented Aug 16, 2022 •
edited
Loading

Yeah, I don't see the value in a global toggle for either feature.

This was referenced Aug 18, 2022
Closed
Closed
@ammario ammario added this to the EE milestone Aug 22, 2022
@ammario ammario mentioned this issue Aug 22, 2022
Closed
@bpmct bpmct mentioned this issue Sep 21, 2022
Closed
@f0ssel f0ssel self-assigned this Oct 11, 2022
@f0ssel f0ssel mentioned this issue Nov 8, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@f0ssel f0ssel

Labels
enterprise Enterprise-license / premium functionality
Projects
None yet
Milestone
EE
Development

Successfully merging a pull request may close this issue.

feat: change template max_ttl to default_ttl coder/coder
6 participants
@sharkymark @misskniss @tjcran @kylecarbs @ammario @f0ssel