<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gitlab on Lykins Blog</title><link>https://blog.lykins.xyz/tags/gitlab/</link><description>Recent content in Gitlab on Lykins Blog</description><generator>Hugo</generator><language>en-us</language><copyright>© Benjamin Lykins</copyright><lastBuildDate>Thu, 28 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lykins.xyz/tags/gitlab/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>