Application changesĪll changes to the application code should be deployed through CI/CD. The following sections describe changes that should be implemented, where possible, through CI/CD. The new stamp should be thoroughly tested as part of the release process before traffic is routed to the stamp via a blue/green deployment strategy. For mission-critical workloads, the changes listed below should result in the deployment of an entirely new stamp. CI/CD is the preferred approach to deploy changes to any environment, Dev/Test, production, and others. Application automationĬontinuous Integration and Continuous Deployment (CI/CD) enables the proper deployment and verification of mission-critical workloads. The following sections describe approaches to handling different types of change. Again, maintenance tasks should be automated and manual tasks should be avoided. The technical execution should take advantage of Azure-native platform capabilities, and the use of automated Azure Pipelines to deploy changes to the application, infrastructure, and configuration. It's crucial for the operational success of a mission-critical workload that the end-to-end responsibilities fall within a single team, the DevOps team.
Organizational alignment is equally important to operation procedures. This article provides operational guidance for making common changes and updates. All changes and maintenance should be applied using deployment pipelines. The application will evolve over time, keys will expire, patches will be released, and more. Like with any application, change will occur in your mission-critical workloads.
0 kommentar(er)
