<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Azure Terraformer - Medium]]></title>
        <description><![CDATA[Exploring Azure, Terraform and tangential technologies with hands-on tutorials, insights, and best practices for automating cloud infrastructure on our favorite cloud, Microsoft Azure. - Medium]]></description>
        <link>https://medium.com/azure-terraformer?source=rss----accbc72a2815---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Azure Terraformer - Medium</title>
            <link>https://medium.com/azure-terraformer?source=rss----accbc72a2815---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:51:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/azure-terraformer" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Turning Log Analytics Into a Business Intelligence Warehouse]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/turning-log-analytics-into-a-business-intelligence-warehouse-fa04b33f3d52?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1983/1*wyIxhJxYvDb3PBP9ERUmCQ.png" width="1983"></a></p><p class="medium-feed-snippet">We have been running Grafana over Azure Monitor for a while now to answer operational questions. Is the platform up, are the pods running&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/turning-log-analytics-into-a-business-intelligence-warehouse-fa04b33f3d52?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/turning-log-analytics-into-a-business-intelligence-warehouse-fa04b33f3d52?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/fa04b33f3d52</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[grafana]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Tue, 08 Sep 2026 14:20:47 GMT</pubDate>
            <atom:updated>2026-09-08T14:20:48.956Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Bridging Terraform and the Azure AI Search Data Plane: Building a First-Class Index Resource]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/bridging-terraform-and-the-azure-ai-search-data-plane-building-a-first-class-index-resource-8aa7c8be330b?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1536/1*oSiVaDTumNBh7MuDWFOirg.png" width="1536"></a></p><p class="medium-feed-snippet">When I implemented the Azure AI Search index resource, the interesting part was not just creating a new Terraform resource.</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/bridging-terraform-and-the-azure-ai-search-data-plane-building-a-first-class-index-resource-8aa7c8be330b?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/bridging-terraform-and-the-azure-ai-search-data-plane-building-a-first-class-index-resource-8aa7c8be330b?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/8aa7c8be330b</guid>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-ai-search]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Fri, 03 Apr 2026 02:24:03 GMT</pubDate>
            <atom:updated>2026-04-03T02:24:05.163Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Workarounds to First-Class Support: Adding Azure AI Search Data Plane Resources to Terraform]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/from-workarounds-to-first-class-support-adding-azure-ai-search-data-plane-resources-to-terraform-aed2dabb919f?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1536/1*zw_NxP13pHGYDGiNd3WqqA.png" width="1536"></a></p><p class="medium-feed-snippet">Sometimes the hardest part of contributing to a Terraform provider is not the resource implementation itself, but figuring out how to&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/from-workarounds-to-first-class-support-adding-azure-ai-search-data-plane-resources-to-terraform-aed2dabb919f?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/from-workarounds-to-first-class-support-adding-azure-ai-search-data-plane-resources-to-terraform-aed2dabb919f?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/aed2dabb919f</guid>
            <category><![CDATA[azure-ai-search]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[azure-ai]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Fri, 03 Apr 2026 01:53:06 GMT</pubDate>
            <atom:updated>2026-04-03T01:53:05.662Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Can’t I Reference Var Sets in Locals? Terraform Stacks, You’re Ironically Killing My DRYness]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/why-cant-i-reference-var-sets-in-locals-terraform-stacks-you-re-ironically-killing-my-dryness-3a59c2f2bbb9?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1536/1*W9hJNpQ-8M1pl57SLKdtMA.png" width="1536"></a></p><p class="medium-feed-snippet">I&#x2019;ve been trying to make my Terraform Cloud (now HCP Terraform) setup cleaner and more reusable by leaning into variable sets &#x2014; a powerful&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/why-cant-i-reference-var-sets-in-locals-terraform-stacks-you-re-ironically-killing-my-dryness-3a59c2f2bbb9?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/why-cant-i-reference-var-sets-in-locals-terraform-stacks-you-re-ironically-killing-my-dryness-3a59c2f2bbb9?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/3a59c2f2bbb9</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[terraform-stacks]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Thu, 05 Feb 2026 04:10:57 GMT</pubDate>
            <atom:updated>2026-02-05T04:11:28.781Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Automating the Forgotten Layer: Entra ID with Terraform Stacks]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/automating-the-forgotten-layer-entra-id-with-terraform-stacks-4dbd41bc967b?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1024/1*4EteTo2hxbt40zwShZ-LgQ.png" width="1024"></a></p><p class="medium-feed-snippet">Most Azure practitioners are very good at automating infrastructure. Subscriptions, networks, compute, and even Azure role assignments are&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/automating-the-forgotten-layer-entra-id-with-terraform-stacks-4dbd41bc967b?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/automating-the-forgotten-layer-entra-id-with-terraform-stacks-4dbd41bc967b?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/4dbd41bc967b</guid>
            <category><![CDATA[azure-active-directory]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[entra-id]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Thu, 05 Feb 2026 03:57:34 GMT</pubDate>
            <atom:updated>2026-02-05T03:57:36.478Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Imagine Phantoms: When Soft-Deleted API Management Breaks Provisioning]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/imagine-phantoms-when-soft-deleted-api-management-breaks-provisioning-1fb8b27f2d32?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1536/1*f3SgpMZmcMhTKJo9qfVeng.png" width="1536"></a></p><p class="medium-feed-snippet">I ran into an issue provisioning API Management, and it was one of those situations where everything looked like a normal deployment&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/imagine-phantoms-when-soft-deleted-api-management-breaks-provisioning-1fb8b27f2d32?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/imagine-phantoms-when-soft-deleted-api-management-breaks-provisioning-1fb8b27f2d32?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/1fb8b27f2d32</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[azure-api-management]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 17:00:43 GMT</pubDate>
            <atom:updated>2026-01-31T16:59:51.242Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[When PROD Must Die but DEV Must Live: A Tale of Terraform Stacks Day 2 Ops]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/when-prod-must-die-but-dev-must-live-a-tale-of-terraform-stacks-day-2-ops-b6ad08c2704d?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1536/1*lk1Kp_CtNjHwA4nWXG1Cfg.png" width="1536"></a></p><p class="medium-feed-snippet">Day 2 operations are where Terraform Stacks starts to feel different from the &#x201C;classic&#x201D; workflow. You&#x2019;re no longer thinking in terms of a&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/when-prod-must-die-but-dev-must-live-a-tale-of-terraform-stacks-day-2-ops-b6ad08c2704d?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/when-prod-must-die-but-dev-must-live-a-tale-of-terraform-stacks-day-2-ops-b6ad08c2704d?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/b6ad08c2704d</guid>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[terraform-stacks]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 16:59:38 GMT</pubDate>
            <atom:updated>2026-01-31T16:59:36.799Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Stop Hardcoding Azure Diagnostic Settings: A Dynamic Terraform Pattern]]></title>
            <link>https://medium.com/azure-terraformer/stop-hardcoding-azure-diagnostic-settings-a-dynamic-terraform-pattern-ccfe7397215a?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/ccfe7397215a</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <dc:creator><![CDATA[Cody Gagnon]]></dc:creator>
            <pubDate>Wed, 21 Jan 2026 17:29:22 GMT</pubDate>
            <atom:updated>2026-01-21T17:29:21.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jDG6nPQh5wAP_KcCCXJWw.jpeg" /></figure><p>Azure’s allLogs category group was introduced to solve a recurring headache: every time Microsoft added a new log category to a resource, you had to update your Terraform code to include it.<strong> </strong>Instead of updating your Terraform every time Microsoft added a new log category, you could set category_group = &quot;allLogs&quot; once and be done.</p><p>So what’s the problem? While support is growing (over 140 resources now support allLogs), Diagnostic Settings remain a patchwork. Storage Blob supports allLogs, but the parent Storage Account has no logs at all. Some resources support AllMetrics, others only individual metrics. The result: you need separate Terraform code for each scenario — or a way to detect support dynamically.</p><h3><strong>The Solution: Let the Azure API Tell You</strong></h3><p>The azurerm_monitor_diagnostic_categories data source reveals exactly what log categories, groups, and metrics a resource supports. With this information, we can write simple conditional logic: when allLogs exists, use it; otherwise, fall back to individual log categories.</p><p>Crucially, this approach checks support at deployment time. If a resource doesn’t support allLogs today but Azure adds it next month, your deployment automatically adapts with no code changes required. By removing the snowflake configuration for each individual Diagnostic Setting resource, we eliminate the guesswork and dramatically reduce the maintenance overhead.</p><h3><strong>Yes, It Works: Terraform Tests on Azure</strong></h3><ul><li><strong>You don’t have to trust me, you can verify it yourself!</strong> Clone the repo &amp; run terraform test to see it in action</li><li><strong>Tests provision actual resources</strong>: Key Vault, Storage Account, Diagnostic Settings</li><li><strong>Assertions validate the logic</strong>:</li></ul><p>✅ Key Vault uses allLogs (has support)<br>✅ Storage Account uses individual metrics (no AllMetrics support or allLogs)<br>✅ Storage Blob uses allLogs (has support)</p><p>In just a few minutes you can confirm the setup logic applies as expected.</p><p><strong>See the tests on </strong><a href="https://github.com/codycodescloud/terraform-azure-diagnostics-patterns/blob/main/tests/integration.tftest.hcl"><strong>GitHub →</strong></a></p><h3>How it Works: The Code</h3><p><strong>Step 1: Query what’s actually supported</strong></p><p>Instead of guessing or checking documentation, use this data source to ask the API directly:</p><pre># Query what this resource actually supports<br>data &quot;azurerm_monitor_diagnostic_categories&quot; &quot;target&quot; {<br>  resource_id = azurerm_key_vault.example.id<br>}<br><br># Azure returns exactly what&#39;s available:<br># - log_category_groups = [&quot;allLogs&quot;, &quot;audit&quot;]<br># - log_category_types  = [&quot;AuditEvent&quot;, &quot;AzurePolicyEvaluationDetails&quot;]  <br># - metrics            = [&quot;AllMetrics&quot;]</pre><p><strong>The key insight:</strong> This data source tells you what’s supported RIGHT NOW, at deployment time.</p><p><strong>Step 2: Adapt Based on What Was Provided</strong></p><p>Use dynamic blocks with conditional logic to choose the optimal configuration:</p><pre>resource &quot;azurerm_monitor_diagnostic_setting&quot; &quot;example&quot; {<br>  name                       = &quot;diag-setting&quot;<br>  target_resource_id         = azurerm_key_vault.example.id<br>  log_analytics_workspace_id = azurerm_log_analytics_workspace.example.id<br>  <br>  # Dynamic logs: Use allLogs if available, otherwise individual categories<br>  dynamic &quot;enabled_log&quot; {<br>    # If &quot;allLogs&quot; exists in log_category_groups → use it<br>    # Otherwise → iterate through all individual log_category_types<br>    for_each = contains(<br>      data.azurerm_monitor_diagnostic_categories.target.log_category_groups,<br>      &quot;allLogs&quot;<br>    ) ? [&quot;allLogs&quot;] : data.azurerm_monitor_diagnostic_categories.target.log_category_types<br>    <br>    content {<br>      # When using allLogs: category = null, category_group = &quot;allLogs&quot;<br>      # When using individual: category = &quot;AuditEvent&quot;, category_group = null<br>      category       = enabled_log.value == &quot;allLogs&quot; ? null : enabled_log.value<br>      category_group = enabled_log.value == &quot;allLogs&quot; ? &quot;allLogs&quot; : null<br>    }<br>  }<br>  <br>  # Dynamic metrics: Same logic for AllMetrics<br>  dynamic &quot;enabled_metric&quot; {<br>    for_each = contains(<br>      data.azurerm_monitor_diagnostic_categories.target.metrics,<br>      &quot;AllMetrics&quot;<br>    ) ? [&quot;AllMetrics&quot;] : data.azurerm_monitor_diagnostic_categories.target.metrics<br>    <br>    content {<br>      category = enabled_metric.value<br>    }<br>  }<br>}</pre><p><strong>What makes this even more powerful</strong>: When Azure adds allLogs support to this resource, the contains() check will return true and your code automatically switches to using it on your next deployment.</p><p><strong>Step 3: Scale to Multiple Resources</strong></p><p>The same pattern works across any number of resources using for_each:</p><pre>locals {<br>  resource_ids = {<br>    storage_account      = azurerm_storage_account.target.id<br>    storage_account_blob = &quot;${azurerm_storage_account.target.id}/blobServices/default/&quot;<br>    key_vault            = azurerm_key_vault.target.id<br>  }<br>}<br><br># Query diagnostic categories for ALL resources at once<br>data &quot;azurerm_monitor_diagnostic_categories&quot; &quot;test&quot; {<br>  for_each    = local.resource_ids<br>  resource_id = each.value<br>}<br><br># Create diagnostic settings for ALL resources<br># Each one automatically uses the optimal strategy<br>resource &quot;azurerm_monitor_diagnostic_setting&quot; &quot;test&quot; {<br>  for_each = data.azurerm_monitor_diagnostic_categories.test<br><br>  name               = &quot;test&quot;<br>  target_resource_id = each.value.id<br>  storage_account_id = azurerm_storage_account.test.id<br><br>  # Same dynamic logic as before - works for ANY resource type<br>  dynamic &quot;enabled_log&quot; {<br>    for_each = contains(each.value.log_category_groups, &quot;allLogs&quot;) ? [&quot;allLogs&quot;] : each.value.log_category_types<br><br>    content {<br>      category       = enabled_log.value == &quot;allLogs&quot; ? null : enabled_log.value<br>      category_group = enabled_log.value == &quot;allLogs&quot; ? &quot;allLogs&quot; : null<br>    }<br>  }<br><br>  dynamic &quot;enabled_metric&quot; {<br>    for_each = contains(each.value.metrics, &quot;AllMetrics&quot;) ? [&quot;AllMetrics&quot;] : each.value.metrics<br><br>    content {<br>      category = enabled_metric.value<br>    }<br>  }<br>}</pre><p><strong>The result</strong>:</p><ul><li>Key Vault automatically gets allLogs + AllMetrics (both supported)</li><li>Storage Blob automatically gets allLogs (supported)</li><li>Storage Account automatically gets individual metrics (no AllMetrics or log categories support)</li></ul><p>All of this behavior is applied from the same code. No resource-specific Diagnostic Setting resources are needed.</p><h3>When This Approach Works Best</h3><p>✅ You want <strong>all available logs and metrics</strong> enabled, with preference for the Azure-managed allLogs + AllMetrics<br>✅ You want automatic adaptation when Azure adds allLogs support<br>✅ You’re okay with the cost of comprehensive logging</p><h3>When You Might Need Customization</h3><p>💡<strong>Selective categories only</strong> (e.g., just AuditEvent for compliance)<br>💡<strong>Cost optimization</strong> (some metrics are expensive)<br>💡<strong>Environment-specific settings</strong> (different rules for dev vs prod)</p><h3>Closing Thoughts</h3><p>This pattern eliminates the maintenance burden of tracking which Azure resources support allLogs and AllMetrics. Most Azure resources, a single Diagnostic Setting resource, and the ability to automatically adapt with no code changes.</p><p><strong>Want to extend this?</strong> I’d love to see PRs on the pattern that add:</p><ul><li>Support for the audit category group</li><li>Logic for per-environment deployments (e.g. dev vs prod</li><li>Selective metric enablement</li></ul><p><a href="https://github.com/codycodescloud/terraform-azure-diagnostics-patterns/tree/main"><strong>GitHub Repository →</strong></a></p><p>Thanks for reading! If this saved you time, let me know in the comments or give the repo a star ⭐. Please consider following me, <a href="https://medium.com/u/c3c2ed64b7ef">Cody Gagnon</a>, for more Terraform goodness! Questions? Open an issue or drop a comment below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccfe7397215a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/azure-terraformer/stop-hardcoding-azure-diagnostic-settings-a-dynamic-terraform-pattern-ccfe7397215a">Stop Hardcoding Azure Diagnostic Settings: A Dynamic Terraform Pattern</a> was originally published in <a href="https://medium.com/azure-terraformer">Azure Terraformer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Terraform Cloud Free Tier is Dead, Long Live the Terraform Cloud Free Tier!!!]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/the-terraform-cloud-free-tier-is-dead-long-live-the-terraform-cloud-free-tier-d40564338f47?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/2600/1*o_Kfw-f1FBrtjefltdZaGw.png" width="3072"></a></p><p class="medium-feed-snippet">The Terraform Cloud Free Tier we knew is going away, but that doesn&#x2019;t mean the concept of &#x201C;free&#x201D; is dead. It&#x2019;s just&#x2026; evolving.</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/the-terraform-cloud-free-tier-is-dead-long-live-the-terraform-cloud-free-tier-d40564338f47?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/the-terraform-cloud-free-tier-is-dead-long-live-the-terraform-cloud-free-tier-d40564338f47?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/d40564338f47</guid>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[terraform-cloud]]></category>
            <dc:creator><![CDATA[Mark Tinderholt]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 16:26:35 GMT</pubDate>
            <atom:updated>2025-12-17T16:26:33.992Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Use Comments in Terraform]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/azure-terraformer/how-to-use-comments-in-terraform-ec7c87c9c2fa?source=rss----accbc72a2815---4"><img src="https://cdn-images-1.medium.com/max/1920/0*OJVl9beXdo1J5nM9.png" width="1920"></a></p><p class="medium-feed-snippet">Learn how to use single-line and multi-line comments in Terraform, with best practices to keep your code clear, maintainable, and easy for&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/azure-terraformer/how-to-use-comments-in-terraform-ec7c87c9c2fa?source=rss----accbc72a2815---4">Continue reading on Azure Terraformer »</a></p></div>]]></description>
            <link>https://medium.com/azure-terraformer/how-to-use-comments-in-terraform-ec7c87c9c2fa?source=rss----accbc72a2815---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec7c87c9c2fa</guid>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Sarah Lean]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 16:25:53 GMT</pubDate>
            <atom:updated>2025-12-17T16:25:36.712Z</atom:updated>
        </item>
    </channel>
</rss>