This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Variables required for the script | |
$orgUrl = "https://dev.azure.com/organisationname" | |
$personalToken = "personalaccesstoken" | |
$projectId = "projectname" | |
# Pass the required authorization ifo using PAT token | |
Write-Host "Initialize authentication context" -ForegroundColor Yellow | |
$token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($personalToken)")) | |
$header = @{authorization = "Basic $token"} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", | |
"contentVersion": "1.0.0.0", | |
"parameters": { | |
"templateContainerUri": { | |
"type": "string", | |
"metadata": { | |
"description": "URI of the Blob Storage Container containing the ARM Templates" | |
} | |
}, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", | |
"contentVersion": "1.0.0.0", | |
"parameters": { | |
"namePrefix": { | |
"type": "string", | |
"metadata": { | |
"description": "Prefix of the resource" | |
} | |
}, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", | |
"contentVersion": "1.0.0.0", | |
"parameters": { | |
"aadClientId": { | |
"type": "string", | |
"metadata": { | |
"description": "Client ID of the AAD B2C Application linked to the API Auth" | |
} | |
}, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
--- | |
Author: chrisreddington | |
Description: Over the past few weeks, I have been working on a number of projects | |
relating to Azure. The usual theme has crept up, around recommended practices, and | |
where to go for documentation. There are a couple of great resources to be aware | |
of! | |
PublishDate: "2016-09-03T12:00:00Z" | |
image: img/cloudwithchrislogo.png | |
categories: | |
- Azure |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
--- | |
Author: chrisreddington | |
Description: "I've recently released a few [Cloud Drops](./series/cloud-drops) episodes on Git related content. The ['Git Behind the Scenes'](./episode/cloud-drops-git-behind-scenes) video was incredibly well received. I'm also aware from my day-to-day discussions that there's a mix of experiences with Git, so also made a [Git 101 Video](./episode/cloud-drops-git-101). In this Cloud World that we live in, version control is an important concept beyond the 'traditional' developers. Infrastructure Engineers can now version control their Infrastructure as Code, or maintenance scripts. Data Scientists can version control their experiments and tests. And of course, developers can version control the code for their software. I also consider version control as a gateway or first step into the world of DevOps. Typically when you think about build and release pipelines, you are triggering based upon some version control event (e.g. a commit to a particular branch, a merge of a pull request, |