Infrastructure as Code (IaC) | All infrastructure changes are made using IaC, are committed to version control system, and reviewed by team members. | |
Deployment Automation | All environment configurations are managed through a central configuration system, and able to be version controlled | |
Configuration Management | All environment configurations are managed through a central configuration system, and able to be version controlled | |
Rollback Strategy: | A deployment rollback plan is well-documented and tested | |
Monitoring Setup | Any new features or changes include necessary logging and monitoring at a technical and business level. Alerts have been set up for any critical or error-level events | |
Performance Metrics | Monitoring and alerting includes performance metrics to ensure the new changes do not degrade system performance | |
Security Checks | All changes comply with security requirements, and have passed security checks and vulnerability scans | |
Disaster Recovery Strategy | Changes include an updated disaster recovery strategy, which aligns with the organization's risk tolerance and business objectives | |
Documentation | All changes and procedures are documented and accessible to the whole team | |
All actions are included in comments | ||
Testing | All changes are tested from development branch on temporary cluster | |
Code base | Prepared code is merged to master branch | |
Peer review | 2 approves are submitted for PR |
Manage space
Manage content
Integrations