Skip to content

Add configurable user dormancy duration #8959

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

Closed
kylecarbs opened this issue Aug 8, 2023 · 2 comments
Closed

Add configurable user dormancy duration #8959

kylecarbs opened this issue Aug 8, 2023 · 2 comments

Comments

@kylecarbs
Copy link
Member

90 days is too long for some of our users. As one mentioned, "you snooze, you lose" and they'd prefer 30 days.

This is a hard-coded duration right now and can easily be converted to a server CLI option.

@ammario
Copy link
Member

ammario commented Aug 8, 2023

Related: #8987

— Also why I don't think we should make this value configurable. Dormancy is purely a license preservation mechanism.

@bpmct
Copy link
Member

bpmct commented Aug 15, 2023

Going to close this out in favor of #8987. I know this is a tricky topic, but since dormant users are only used to deoccupy a license seat (when they are logged in, they are marked as active again, and can access all their workspaces) we are going to keep it hardcoded to 90 days. This is a standard number for other software such as GitLab and Coder v1.

We are working on other features to clean up Coder deployments such as #7095.

If you want to free up license seats, you can build custom scripts to delete workspaces, delete users, or suspend users based on their last_seen value

@bpmct bpmct closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants