Skip to content
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

loft template to terminate port-forwarding after specificed time #71

Open
blairham opened this issue Nov 12, 2020 · 4 comments
Open

loft template to terminate port-forwarding after specificed time #71

blairham opened this issue Nov 12, 2020 · 4 comments

Comments

@blairham
Copy link

blairham commented Nov 12, 2020

Issue
While the dev command is super useful, it falls short when a user has left open a devspace dev as the port forwarding keeps the space active and never lets it sleep or delete.

Expected
Adding a template that would put a time limit on port forwarding, so that a space can sleep appropriately and eventually be deleted

@FabianKramm
Copy link
Member

@blairham thanks for reporting this! I'm not exactly sure if I understand this correctly, what do you mean by template? Do you want a timeout for the devspace dev command that basically interrupts port-forwarding and sync after a certain time period? Another possibility would be that loft could ignore still open connections for a space and not count these as activity, this could be enabled and disabled via an annotation on the space.

@blairham
Copy link
Author

@FabianKramm yes, I'm looking for a way to timeout the dev command, it seems that people just leave that running and don't ever terminate it which leaves that space around forever until I manually terminate it. The latter idea seems like the most ideal option in my opinion.

@FabianKramm
Copy link
Member

@blairham I see, yes we'll add an option to ignore still open connections for sleep mode in the next loft relase

@blairham
Copy link
Author

blairham commented Nov 18, 2020

@FabianKramm I was thinking about this and it might also be worth considering adding a timeout section in the devspace.yaml dev section. Then we could just set a timeout level there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants