How do I provision Automated rollbacks in Azure with Ansible?

Provisioning automated rollbacks in Azure using Ansible allows for quick recovery from failed deployments. This ensures high availability and reliability of your applications. The following example demonstrates how to set up a rollback mechanism.

- name: Deploy application hosts: azure tasks: - name: Deploy latest version azure_rm_webapp: resource_group: myResourceGroup name: myWebApp app_service_plan_id: myAppServicePlan site_config: default_documents: - index.html linux_fx_version: "NODE|12-lts" always_on: true src: /path/to/application.zip register: app_deployment - name: Check deployment status debug: var: app_deployment - name: Rollback if deployment failed azure_rm_webapp: resource_group: myResourceGroup name: myWebApp app_service_plan_id: myAppServicePlan src: /path/to/previous_version.zip when: app_deployment.failed

Azure Ansible automated rollbacks deployments azure_rm_webapp rollback mechanism

Related Questions

How do I avoid rehashing overhead with std::set in multithreaded code?

How do I find elements with custom comparators with std::set for embedded targets?

How do I erase elements while iterating with std::set for embedded targets?

How do I provide stable iteration order with std::unordered_map for large datasets?

How do I reserve capacity ahead of time with std::unordered_map for large datasets?

How do I erase elements while iterating with std::unordered_map in multithreaded code?

How do I provide stable iteration order with std::map for embedded targets?

How do I provide stable iteration order with std::map in multithreaded code?

How do I avoid rehashing overhead with std::map in performance-sensitive code?

How do I merge two containers efficiently with std::map for embedded targets?