<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resource Tags on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/tags/resource-tags/</link><description>Recent content in Resource Tags on Incredible Technology, Incredibly Simple</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 23 Jul 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://damianflynn.com/tags/resource-tags/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Tags as Bicep Parameters</title><link>https://damianflynn.com/posts/bicep-tags-as-parameters/</link><pubDate>Fri, 23 Jul 2021 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/bicep-tags-as-parameters/</guid><description>&lt;p&gt;A deployment often needs to find infrastructure that already exists. A virtual machine might belong to a subscription with a shared Recovery Services vault, while its backup policy depends on the workload. Passing the vault name, its resource group and the policy name into every deployment works, but repeats configuration that may already be recorded in Azure.&lt;/p&gt;
&lt;p&gt;In the earlier post, &lt;a href="https://damianflynn.com/posts/azure-iac-tags-as-parameters/" rel=""&gt;Azure Tags as ARM Template Parameters&lt;/a&gt;, I used tags to look up those values from an ARM JSON template. This is the same lab scenario expressed in Bicep. The lookup behaves the same way, but the string interpolation makes the resource paths easier to follow.&lt;/p&gt;</description></item><item><title>Azure Tags as ARM Template Parameters</title><link>https://damianflynn.com/posts/azure-iac-tags-as-parameters/</link><pubDate>Sun, 17 Jan 2021 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/azure-iac-tags-as-parameters/</guid><description>&lt;h1 class="relative text-5xl font-semibold leading-tense text-secondary-500 mb-4 -ml-px" id="azure-as-a-state-machine-dogfooding-tags"&gt;&lt;a href="#azure-as-a-state-machine-dogfooding-tags" class="header-mark" aria-label="Header mark for 'Azure as a State Machine, dogfooding Tags'"&gt;&lt;/a&gt;
 &lt;div id="azure-as-a-state-machine-dogfooding-tags" class="absolute -top-28"&gt;&lt;/div&gt;
 Azure as a State Machine, dogfooding Tags
&lt;/h1&gt;
&lt;p&gt;In the post, I am going to introduce a concept which will allow you to greatly up your Infrastructure as Code game, by using Azure as a State Machine!&lt;/p&gt;
&lt;p&gt;One of the typical challenges when deploying ARM templates, is the sheer number of parameters which we find as a requirement to complete a deployment; which as you will appreciate gets considerably harder as we target many environments.&lt;/p&gt;</description></item><item><title>Appending Tags to Azure Resources with ARM Templates</title><link>https://damianflynn.com/posts/azure-iac-appending-tags/</link><pubDate>Wed, 01 Apr 2020 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/azure-iac-appending-tags/</guid><description>&lt;p&gt;Todays conundrum: As I am leveraging templates, there will always be some standard tags I require to implement within the template, but I also require to provide additional tags as a parameter to be appended with the deployment.&lt;/p&gt;
&lt;p&gt;My objective is to set up tags within an ARM template in accordance with good governance and the Cloud adoption framework.&lt;/p&gt;
&lt;h2 class="relative text-3xl font-bold leading-tight text-secondary-500 mb-2 mt-12 -ml-px"&gt;
 &lt;div id="solution" class="absolute -top-28"&gt;&lt;/div&gt;
 Solution
&lt;/h2&gt;
&lt;p&gt;ARM Template functions to the rescue. Todays salvation is called &lt;code&gt;union&lt;/code&gt;, which you can learn more about on the actual [reference site][https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-functions-array#union]&lt;/p&gt;</description></item></channel></rss>