Azure Artifacts – Scripted Deployments and DevOps Automation
In software development, it is common to want to share code or even pre-built components that execute specific tasks. For example, if a developer has built a function that performs a complex calculation, you may wish to share that with other developers as an artifact so that they can re-use it. This is different from …
Azure Artifacts – Scripted Deployments and DevOps AutomationRead More
Azure Pipelines – Scripted Deployments and DevOps Automation
We can build and deploy components in Azure from ARM templates using PowerShell or the Azure CLI by using the New-AzResourceGroupDeployment or az deployment group create commands. Azure Pipelines provides on-demand VM nodes with the necessary tooling installed to perform our deployments. In other words, rather than running the required PowerShell or Azure CLI scripts …
Azure Pipelines – Scripted Deployments and DevOps AutomationRead More
Azure Repos – Scripted Deployments and DevOps Automation
Azure Repos allows you to control and manage code changes by enforcing versioning and tracking of changes across files. Code is stored in a repository and repositories use branches to provide an additional layer of management. Each repository has at least one branch; by default, this is called the master branch. When a user wishes …
Azure Repos – Scripted Deployments and DevOps AutomationRead More
Looking at Azure DevOps – Scripted Deployments and DevOps Automation
Throughout this chapter, we have been looking at how we can encode infrastructure in script files and ARM templates that then allow us to automate deployments using those artifacts. This process is often referred to as Infrastructure as Code (IaC) and fits well with agile-based delivery mechanisms as it provides the ability to build solutions …
Looking at Azure DevOps – Scripted Deployments and DevOps AutomationRead More
Understanding ARM templates – Scripted Deployments and DevOps Automation-2
For example, in the preceding ARM template example for creating a storage account, we generate the storage account name using the text store followed by a GUID: “variables”: { “storageAccountName”: “[concat(‘store’, uniquestring(resourceGroup().id))]” }, Further complexity can be added using conditional statements using the following format: “condition”: “[equals(parameters(‘<someparameter>’),'<somevaluetotestfor>’)]” For example, you can test for the value …
Understanding ARM templates – Scripted Deployments and DevOps Automation-2Read More
Understanding ARM templates – Scripted Deployments and DevOps Automation-1
Just as other tools are simply wrappers for the Azure REST APIs, everything that is built in Azure is defined as an ARM template. Whether you create a service through the Azure portal, PowerShell, REST APIs, or the CLI, ultimately that service is described within an ARM template. An ARM template is a JSON-based text …
Understanding ARM templates – Scripted Deployments and DevOps Automation-1Read More
Choosing between PowerShell and the Azure CLI – Scripted Deployments and DevOps Automation
When we start to consider automating the deployment and management of resources in Azure, the first option would be using the command line, and here we then have two further options: PowerShell and the Azure CLI. PowerShell and the CLI are very similar: they both run from a command prompt, they both allow access to …
Choosing between PowerShell and the Azure CLI – Scripted Deployments and DevOps AutomationRead More
Looking at the Azure REST API – Scripted Deployments and DevOps Automation
The first option we will consider is the Azure REST API. All actions on Azure resources are managed through ARM, and this is exposed by a set of APIs. When we perform actions in the Azure portal, we are actually making HTTP calls to the REST APIs. Information Note Representational State Transfer (REST) is an …
Looking at the Azure REST API – Scripted Deployments and DevOps AutomationRead More
Exploring provisioning options – Scripted Deployments and DevOps Automation
In Chapter 16, Developing Business Continuity, we looked at how to ensure our solutions have adequate backups in the event that the unexpected happens. In this chapter, we continue the operational theme, looking at how we can deploy components into Azure, specifically using scripts, templates, and automation tools. We will begin by exploring what options …
Exploring provisioning options – Scripted Deployments and DevOps AutomationRead More
Understanding the data archiving options – Developing Business Continuity
Many organizations have a requirement to hold some data for longer periods of time. This may be for compliance reasons or simply for long-term record retention. Although backup solutions do offer long-term retention options, for archival purposes Azure Storage offers a specific archiving tier. We covered the storage tiers in Chapter 9, Exploring Storage Solutions, …
Understanding the data archiving options – Developing Business ContinuityRead More
