https://markallison.co.uk/tags/azure-pipelines/ Recent content in Azure-Pipelines on Mark Allison https://markallison.co.uk/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E https://markallison.co.uk/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E Hugo -- 0.151.2 en Fri, 04 Mar 2022 07:30:29 +0000 https://markallison.co.uk/blog/azure-pipelines-variables/ Fri, 04 Mar 2022 07:30:29 +0000 https://markallison.co.uk/blog/azure-pipelines-variables/ <h2 id="question">Question</h2> <p>Where should variables be stored for deploying <em>infrastructure-as-code</em> in Azure DevOps pipelines to Azure? Resources need to be deployed to different regions and environments, and attributes for these need to be stored somewhere.</p> <h2 id="options">Options</h2> <p>Six options spring to mind.</p> <ol> <li><strong><a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/parameter-files">Parameter files</a></strong>. Seems like the obvious choice.</li> <li><strong><a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/parameters#default-value">Template file defaults</a></strong> in <code>azuredeploy.json</code> or <code>main.bicep</code></li> <li><strong><a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/library/variable-groups?view=azure-devops&amp;tabs=yaml">Azure DevOps Library</a></strong> variable groups. Seems good, a single place</li> <li><strong><a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&amp;tabs=yaml%2Cbatch">Azure Pipelines variables</a></strong> in individual pipelines</li> <li><strong><a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-files#loadtextcontent">Configuration file</a></strong> within the project source code</li> <li><strong><a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/runtime-parameters?view=azure-devops&amp;tabs=script">Runtime parameters</a></strong> for setting values at run time</li> </ol> <p>Let&rsquo;s go through each option and then discuss my preferred approach.</p> https://markallison.co.uk/blog/deploy-bicep-with-azure-devops/ Sun, 11 Apr 2021 21:08:20 +0100 https://markallison.co.uk/blog/deploy-bicep-with-azure-devops/ <h2 id="goodbye-json">Goodbye JSON</h2> <p>Since Microsoft released <a href="https://github.com/Azure/bicep">bicep version 0.3</a> I thought I&rsquo;d give it a try because anyone that&rsquo;s authored ARM templates will know, they tend to make your eyes bleed after a while.</p> <blockquote> <p>Bicep aims to drastically simplify the authoring experience with a cleaner syntax, improved type safety, and better support for modularity and code re-use.</p> </blockquote> <p>I&rsquo;m sold!</p> <p>I reverse-engineered an existing simple template that deploys two storage accounts by using <code>bicep decompile</code> and got a template like this:</p>