Skip to content

scheduling: ephemeral workspaces that auto-delete #5572

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
bpmct opened this issue Jan 4, 2023 · 2 comments
Closed

scheduling: ephemeral workspaces that auto-delete #5572

bpmct opened this issue Jan 4, 2023 · 2 comments
Assignees
Labels
stale This issue is like stale bread.

Comments

@bpmct
Copy link
Member

bpmct commented Jan 4, 2023

When I'm trying to reproduce an issue on a specific environment or just tinkering, I'd love to be able to create an ephemeral workspace that can just clean itself up after I'm done using it.

This also has some cool use cases for Coder in CI/CD where a Coder preview workspace can be created when a PR is created.

Screen Shot 2023-01-04 at 6 51 05 AM

@mattlqx
Copy link

mattlqx commented Jan 4, 2023

I'd like a lifecycle control for this based on inactivity. e.g. If someone hasn't used the workspace for 30 days, delete it.

There's a finer point also of can an admin enforce these settings.

@ammario ammario changed the title Ephemeral workspaces that auto-delete scheduling: ephemeral workspaces that auto-delete Feb 6, 2023
@github-actions
Copy link

github-actions bot commented May 8, 2023

This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.

@github-actions github-actions bot added the stale This issue is like stale bread. label May 8, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale This issue is like stale bread.
Projects
None yet
Development

No branches or pull requests

3 participants