<?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 Lykins Blog</title><link>https://blog.lykins.xyz/tags/terraform/</link><description>Recent content in Terraform on Lykins Blog</description><generator>Hugo</generator><language>en-us</language><copyright>© Benjamin Lykins</copyright><lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lykins.xyz/tags/terraform/index.xml" rel="self" type="application/rss+xml"/><item><title>Codified Observability — Layer 3: Provisioning</title><link>https://blog.lykins.xyz/posts/codified-observability-provisioning/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.lykins.xyz/posts/codified-observability-provisioning/</guid><description>&lt;p&gt;This is part 4 of a series based on my DevOpsCon San Diego 2026 talk. &lt;a href="https://blog.lykins.xyz/posts/codified-observability-platforms/"&gt;Part 3&lt;/a&gt; put the LGTM stack on Nomad. This post is Layer 3 — Provisioning: dashboards and alerts that ship with the service, not weeks later.&lt;/p&gt;
&lt;p&gt;The code lives in &lt;a href="https://gitlab.com/lykins/devopscon-2026/-/tree/main/3-terraform"&gt;&lt;code&gt;3-terraform/&lt;/code&gt;&lt;/a&gt; of the &lt;a href="https://gitlab.com/lykins/devopscon-2026"&gt;devopscon-2026&lt;/a&gt; lab.&lt;/p&gt;
&lt;h2 id="the-secondary-step"&gt;The Secondary Step&lt;/h2&gt;
&lt;p&gt;Infrastructure deploys. The dashboard gets added later. Alert thresholds are set by gut feel and never reviewed. The dashboard only lives in Grafana — not in git. Observability config has no ownership and no history.&lt;/p&gt;</description></item><item><title>Scaling Terraform Test in GitLab</title><link>https://blog.lykins.xyz/posts/scaling-terraform-test-gitlab/</link><pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate><guid>https://blog.lykins.xyz/posts/scaling-terraform-test-gitlab/</guid><description>&lt;p&gt;As Terraform module counts grow, testing stops being a &amp;ldquo;nice to have&amp;rdquo; and becomes the thing that either keeps your platform honest or quietly falls apart. The hard part is rarely writing a single &lt;code&gt;terraform test&lt;/code&gt; file — it is making that pattern repeatable across every resource module, every composite module, and every merge request without copying CI logic into a dozen repos or hundreds of repos.&lt;/p&gt;
&lt;p&gt;I put together a small public GitLab group, &lt;a href="https://gitlab.com/terraform-test662822"&gt;terraform-test&lt;/a&gt;, to walk through one way to scale this: resource-specific modules, composite modules that compose them into a solution, and a shared CI template that runs &lt;code&gt;terraform test&lt;/code&gt; the same way everywhere.&lt;/p&gt;</description></item><item><title>Terraform Professional + HashiConf Talk</title><link>https://blog.lykins.xyz/posts/terraform-professional-hashiconf-talk/</link><pubDate>Wed, 28 Aug 2024 00:00:00 +0000</pubDate><guid>https://blog.lykins.xyz/posts/terraform-professional-hashiconf-talk/</guid><description>&lt;p&gt;Just a short little update today. I am going to be documenting a new series of blog posts.&lt;/p&gt;
&lt;h2 id="hashicorp-certified-terraform-authoring-and-operations-professional"&gt;HashiCorp Certified: Terraform Authoring and Operations Professional&lt;/h2&gt;
&lt;p&gt;Took the test as part of the beta program a while back and finally got a result :)&lt;/p&gt;
&lt;p&gt;It was a fun opportunity and would recommend others to give it a shot!&lt;/p&gt;
&lt;p&gt;&lt;img src="https://dev-to-uploads.s3.amazonaws.com/uploads/articles/orx1b5xvs02tmls5uasc.png" alt="HashiCorp Certified: Terraform Authoring and Operations Professional"&gt;&lt;/p&gt;
&lt;h2 id="hashiconf-presentation"&gt;HashiConf Presentation&lt;/h2&gt;
&lt;p&gt;So back when a call for presenters went out for HashiConf, I put out a short topic on learning Nomad. It is one of the Hashi products which has intrigued me the most. I just have not had a reason or opportunity to work with it. Especially with 2 kids aged 3 and under, the amount of free time I have to learn something new is limited.&lt;/p&gt;</description></item><item><title>Terraform Cloud Agents - Podman</title><link>https://blog.lykins.xyz/posts/tfc-agents-podman/</link><pubDate>Fri, 16 Feb 2024 00:00:00 +0000</pubDate><guid>https://blog.lykins.xyz/posts/tfc-agents-podman/</guid><description>&lt;p&gt;Question came up if Podman could run Terraform Cloud agents. Assumption would be yes, but surprisingly I did not see anyone posts or documentation on it. For those who do not care to read through this, the answer is yes.&lt;/p&gt;
&lt;h1 id="introduction---terraform-agents-agents"&gt;Introduction - Terraform Agents Agents&lt;/h1&gt;
&lt;p&gt;If you are not familiar with Terraform Cloud agents, they are essentially ways to extend runs from Terraform Cloud/Enterprise within a private network.&lt;/p&gt;
&lt;p&gt;Runs are pulled by the agents.&lt;/p&gt;</description></item><item><title>Terraform Removed Block</title><link>https://blog.lykins.xyz/posts/tf-removed/</link><pubDate>Thu, 07 Dec 2023 20:59:45 -0500</pubDate><guid>https://blog.lykins.xyz/posts/tf-removed/</guid><description>&lt;p&gt;Decided to test out the new state block which looks to be released in v1.7.&lt;/p&gt;
&lt;p&gt;Stemmed from this request in the hashi forums.
&lt;a href="https://discuss.hashicorp.com/t/request-for-testing-removed-block/60511"&gt;https://discuss.hashicorp.com/t/request-for-testing-removed-block/60511&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For now, you can find some documentation and usage here:
&lt;a href="https://github.com/hashicorp/terraform/pull/34339/commits/9af31fb5ce8fe983fc212390659215cf6501c85d"&gt;https://github.com/hashicorp/terraform/pull/34339/commits/9af31fb5ce8fe983fc212390659215cf6501c85d&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;At this point it looks like a holy trinity of state blocks will be finished - import, moved, and now removed.&lt;/p&gt;
&lt;p&gt;I conducted a simple test, and similar to import and move, additional feature support has been added.&lt;/p&gt;</description></item></channel></rss>