Lock environments to prevent autodeploy
Description
With the introduction of environment and autodeploy, it's hard to prevent autodeploy to go through for some special circonstances (incident, deployment of a sensitive feature).
Proposal
It would be nice to be able to lock an environment which will make next autodeploy fallback to manual. A default lock would lock the environment for XX minutes. The user would also be able to customize the lock duration.
We would show in a nice UI (red lock icon) what environments is locked and by who (avatar image).
It would also be nice if we could lock multiples environments at once like :
api/apiv1
api/apiv2
api/apiv3
In this case i would like to lock all api/
environments so api/apiv1
+ api/apiv2
+ api/apiv3
.
I think we should have a project option to specify unlock options.
- Any collaborators users can unlock a environments locked by someone else.
Or
- Only lock creator can unlocked his own lock.
Regards,