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

Allow per-environment idling (instead of per-project) #980

Closed
tobybellwood opened this Issue Mar 21, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@tobybellwood
Copy link

tobybellwood commented Mar 21, 2019

Currently Lagoon only allows you to idle environments on a per-project basis - i.e. all on or all off.

It'd be great to be able to set individual environments to non-idle (e.g. for cron testing etc as per #949, or for running larger test plans) - this would also give us more ability to mitigate the costs involved in projects with multiple environments.

@twardnw twardnw self-assigned this Mar 21, 2019

@Schnitzel Schnitzel assigned twardnw and unassigned twardnw Mar 21, 2019

twardnw added a commit that referenced this issue Mar 22, 2019

twardnw added a commit that referenced this issue Mar 22, 2019

@twardnw twardnw referenced this issue Mar 22, 2019

Merged

980 autoidle environments #985

3 of 3 tasks complete

twardnw added a commit that referenced this issue Mar 22, 2019

twardnw added a commit that referenced this issue Mar 27, 2019

@tobybellwood

This comment has been minimized.

Copy link
Author

tobybellwood commented Mar 28, 2019

woohoo! nice work @twardnw 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.