<?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 Luis Sousa Blog</title>
    <link>https://89393b0c.nuvai-blog.pages.dev/tags/terraform/</link>
    <description>Recent content in Terraform on Luis Sousa Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 07 Mar 2026 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://89393b0c.nuvai-blog.pages.dev/tags/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Managing Cloudflare www-to-apex redirects with Terraform for WordPress SEO</title>
      <link>https://89393b0c.nuvai-blog.pages.dev/posts/cloudflare-www-to-apex-redirects-terraform/</link>
      <pubDate>Sat, 07 Mar 2026 12:00:00 +0000</pubDate>
      <guid>https://89393b0c.nuvai-blog.pages.dev/posts/cloudflare-www-to-apex-redirects-terraform/</guid>
      <description>&lt;p&gt;For SEO, &lt;code&gt;www.example.com&lt;/code&gt; should 301 redirect to &lt;code&gt;example.com&lt;/code&gt; so search engines see one canonical host. We manage our travel blog&amp;rsquo;s infrastructure with Terraform, including Cloudflare. When we tried to add the www-to-apex redirect, we hit &amp;ldquo;exceeded maximum number of zone rulesets.&amp;rdquo; Here&amp;rsquo;s how we fixed it and manage redirects as code.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-terraform-for-cloudflare&#34;&gt;&#xA;  Why Terraform for Cloudflare&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#why-terraform-for-cloudflare&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Terraform gives you versioned, repeatable config. No manual dashboard drift, no &amp;ldquo;who changed what&amp;rdquo; surprises. Redirects live in &lt;code&gt;main.tf&lt;/code&gt; and are applied consistently.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
