{"id":439,"date":"2020-10-05T00:00:00","date_gmt":"2020-10-05T00:00:00","guid":{"rendered":""},"modified":"2025-06-30T08:06:18","modified_gmt":"2025-06-30T15:06:18","slug":"enabling-resilient-devops-practices-with-code-to-cloud-automation","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/enabling-resilient-devops-practices-with-code-to-cloud-automation\/","title":{"rendered":"Enabling resilient DevOps practices with code to cloud automation"},"content":{"rendered":"\n

This blog post was co-authored by Usha Narayanabhatta, Product Manager, GitHub.<\/em><\/p>\n\n\n\n

As digital transformation has evolved, so have customer expectations. Enterprises are expected to deliver continuous value by releasing frequent bug-proof updates with little to no disruption to their userbase. This is no small feat, as nations and governments roll out stringent new data and security measures.<\/p>\n\n\n\n

So how are enterprises able to ship faster while maintaining governance, security, and compliance standards amidst a pandemic that has forced work to be remote?<\/p>\n\n\n\n

Based on the Enterprise DevOps 2020-2021<\/a> report, 80 percent of top-performing enterprises surveyed say they have begun \u201cshifting-left,\u201d or automating governance, security, and compliance into the early stages of their software development lifecycles (SDLC). These enterprises are not only automating their build and release workflows, but they\u2019re also adopting an \u201ceverything-as-code\u201d mindset. This shift means that not just infrastructure configurations and release pipelines, but also compliance and security policies, are written \u201cas code,\u201d enabling continuous improvement, while promoting better re-use, resilience, and driving greater transparency.<\/p>\n\n\n\n

It\u2019s with all this in mind that we continue to refine, update, and add to our GitHub Actions portfolio. At Microsoft Ignite<\/a> we announced new GitHub Actions for Azure, which we added to our growing catalogue of Azure and GitHub integrations<\/a>, with more to come soon. GitHub Actions for Azure enables deployments to multiple Azure services\u2014from web applications to serverless functions to Kubernetes, to Azure SQL and MySQL databases\u2014ultimately helping enterprises stay resilient while giving the flexibility to build an automated workflow to manage your SDLC.<\/p>\n\n\n\n

Manage Azure Policy as Code in GitHub<\/h2>\n\n\n\n

As you progress on your Cloud Governance journey, there is an increasing need to shift from manually managing each policy in the Azure portal to something more manageable, collaborative, and repeatable at enterprise scale. We are announcing that we made the integration between Azure Policy and GitHub even stronger to help you on this journey. You can now easily export Azure policies to a GitHub repository in just a few clicks. All exported policies will be stored as files in GitHub. You can then collaborate and track changes using version control and push policy file changes to Azure Policy using Manage Azure Policy<\/a> action. See Managing Azure Policy as Code with GitHub<\/a> to learn more and go to Azure Policy<\/a> to access the feature.<\/p>\n\n\n\n

\"Export<\/figure>\n\n\n\n

Deploy ARM infrastructure as code<\/h2>\n\n\n\n

With the move to the cloud, many teams need to repeatedly deploy their solutions to the cloud and ensure their infrastructure is in a reliable state. To meet these challenges, you can automate deployments by defining the infrastructure that needs to be deployed as code with Azure Resource Management (ARM) templates.<\/p>\n\n\n\n

To address this, we are releasing a Deploy Azure Resource Manager Template action<\/a>. With this action you can automate your workflow to deploy ARM templates and manage Azure resources. This action can be used to deploy ARM templates at any deployment scope<\/a>; resource group, subscription or at a management group scope. The output of this ARM deployment action can be used in subsequent actions within the workflow as well for further processing.<\/p>\n\n\n\n

\"Deploy<\/figure>\n\n\n\n

Build Azure Virtual Machine Images for immutable infrastructure<\/h2>\n\n\n\n

With the newly rolled out Build Azure Virtual Machine Image<\/a> action, customizing, creating, and distributing virtual machine (VM) images just got easier. You can now use this action to create custom VM images that hold artifacts produced in your Continuous Delivery workflows, distribute them as a Shared Image Gallery<\/a> version or a managed image or a virtual hard disk (VHD) and get complete traceability between the GitHub and Azure portal<\/a>.<\/p>\n\n\n\n

\"Virtual<\/figure>\n\n\n\n

Trace Kubernetes changes from Azure portal to GitHub commits<\/h2>\n\n\n\n

Deploy to Kubernetes cluster action<\/a> is now enhanced to enable a changelog view in the Azure portal to trace any deployment done on an Azure Kubernetes Service (AKS) cluster from the exact GitHub commits and issues that got deployed all the way to the specific GitHub workflow that was used to deploy the changes.<\/p>\n\n\n\n

\"A<\/figure>\n\n\n\n

Scan container images as part of Pull Request workflows<\/h2>\n\n\n\n

You can now add the container scanning action<\/a> to your workflows and add additional checks to secure the Docker images created as part of Continuous Integration (CI) or Pull Request (PR) workflows. This helps developers scan for a common vulnerabilities in their Docker images and gain confidence before pushing to a container registry or deploying to a containerized web app or a Kubernetes cluster.<\/p>\n\n\n\n

\"Container<\/figure>\n\n\n\n

Get started<\/h2>\n\n\n\n

Check out the documentation for Azure Policy integration with GitHub<\/a>, Azure Virtual Machine deployments<\/a>, Deploy ARM Template action<\/a>, and Container Scanning Action<\/a> to get started.<\/p>\n\n\n\n

Also, feel free to explore the improved DevOps starter<\/a> experience which now supports GitHub Actions as a CI\/CD provider. This new enhancement allows developers to set up an end-to-end GitHub workflow for a sample application with just four simple steps.<\/p>\n\n\n\n

If you have any changes you\u2019d like to see or suggestions for these features, then we\u2019d love your feedback as well as contributions to the GitHub Action repositories<\/a>\u2014we\u2019re taking pull requests. If you encounter a problem with any specific action, you can also open an issue on the action repository.<\/p>\n\n\n\n