<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>terraform on Aos Dabbagh</title>
    <link>/tags/terraform/</link>
    <description>Recent content in terraform on Aos Dabbagh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 25 Feb 2023 16:19:04 -0500</lastBuildDate><atom:link href="/tags/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Better Utilization of Terraform Resource Keys</title>
      <link>/2023/02/25/better-utilization-of-terraform-resource-keys/</link>
      <pubDate>Sat, 25 Feb 2023 16:19:04 -0500</pubDate>
      
      <guid>/2023/02/25/better-utilization-of-terraform-resource-keys/</guid>
      <description>When managing multiple dissimilar resources in Terraform, best practices dictate that you use the for_each meta-argument. Furthermore, when needing to convert a list to a set or map for chaining, the advice given is usually of the form:
for_each = { for k, v in aws_subnet.all : k =&amp;gt; v } This will work but unfortunately it becomes unwieldy the more you need to rely on these generated resources.
A motivating example In one of Adrian Cantrill&amp;rsquo;s excellent courses on AWS, we are tasked with setting up a multi-tier subnet design:</description>
    </item>
    
  </channel>
</rss>
