<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Choice on Humayun Manzer</title><link>https://humayunhub.com/tags/choice/</link><description>Recent content in Choice on Humayun Manzer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 23 Jul 2025 18:00:00 +0800</lastBuildDate><atom:link href="https://humayunhub.com/tags/choice/index.xml" rel="self" type="application/rss+xml"/><item><title>Terraform count vs for_each: A Friendly Guide (+ Cheatsheet)</title><link>https://humayunhub.com/blog/2025/terraform_count_foreach/</link><pubDate>Wed, 23 Jul 2025 18:00:00 +0800</pubDate><guid>https://humayunhub.com/blog/2025/terraform_count_foreach/</guid><description>&lt;div class="paragraph">

 &lt;small>&lt;i>&lt;a href="https://unsplash.com/photos/a-couple-of-toy-cars-sitting-on-top-of-a-table-3pxbdA4XGFQ?utm_content=creditShareLink&amp;amp;utm_medium=referral&amp;amp;utm_source=unsplash">Photo credit&lt;/a>&lt;/i>&lt;/small>

&lt;/div>
&lt;div class="paragraph">
&lt;p>Choosing between &lt;code>count&lt;/code> and &lt;code>for_each&lt;/code> in Terraform looks simple at first, but it can change how predictable your infrastructure is over time. I’ve been bitten by both approaches in the past, so here’s a practical guide to when each one makes sense, with examples and a quick cheatsheet.&lt;/p>
&lt;/div></description></item></channel></rss>