<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>#Arm on gripdev.xyz</title>
    <link>http://blog.gripdev.xyz/tag/%23arm/</link>
    <description>Recent content in #Arm on gripdev.xyz</description>
    <generator>Hugo -- 0.153.2</generator>
    <language>en</language>
    <lastBuildDate>Thu, 21 Jun 2018 10:49:25 +0000</lastBuildDate>
    <atom:link href="http://blog.gripdev.xyz/tag/%23arm/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From ARM to Terraform: Why I&#39;m becoming a Terraform convert</title>
      <link>http://blog.gripdev.xyz/2018/06/21/from-arm-to-terraform-why-im-becoming-a-terraform-convert/</link>
      <pubDate>Thu, 21 Jun 2018 10:49:25 +0000</pubDate>
       <guid isPermaLink="false">http://blog.gripdev.xyz/?p=1149</guid> 
      <description>&lt;p&gt;Let me give you some background: I’ve been a heavy user of the &lt;a href=&#34;https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview&#34;&gt;Azure Resource Manager (ARM) template&lt;/a&gt; s for some time now. We’ve had some good times together. We’ve also had some bad times and boy have we seriously fallen out at times!&lt;/p&gt;
&lt;p&gt;I’ve used ARM extensively to automate deployment, configuration and update of the infrastructure in Azure. I’ve used it on everything from single-person projects to large scale dual-region deployments of services with critical live traffic.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
