Revert and rollback Auto Remediation deployments in case of problems
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
Problem to solve
Auto Remediation is able to automatically fix vulnerabilities and deploy these changes to production.
GitLab should monitor the production environment and, if error rates increase or performances decrease, revert the changes in the codebase and rollback the deployment to the previous stable one.
- Devon, DevOps Engineer
- Sidney, Systems Administrator
- Sam, Security Analyst
GitLab should use existing monitoring features to detect problems with the new deployment. Anyway, it also needs to have specific information about the changes to revert them.
Provide information to allow rollback in case of bad performances of a new deployment triggered by Auto Remediation.
Revert changes in the codebase.