Environment locking prevents any change to the environment. While the environment is locked no deploy, destroy, plan or drift detection actions will be run.Documentation Index
Fetch the complete documentation index at: https://docs.envzero.com/llms.txt
Use this file to discover all available pages before exploring further.
Who can lock and release environments
To lock or release an environment, a user needs theLock/Unlock Environment permission (part of the default “Project Admin” role.
Any user with this permission can release the lock, regardless of who locked it.
How to use
What happens when the environment is locked
- User cannot run Deploy, Destroy or Ad hoc Task
- Scheduled Deploy, Destroy, and Drift Detection will not run. They will resume after unlocking.
- Continuous Deployment, Plan on Pull Request, and Plan and Apply from PR Comments will not work.
- Environment will not be destroyed due to TTL. After unlocking, a notification will be sent as usual, before the environment is destroyed.
Next steps
- Managing Bulk Operations - Lock or unlock multiple environments at once.
- Deployment Scheduling - Schedule deploys and destroys that resume after unlocking.
- Environment Overview - Review all available environment actions and states.