<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vault on jen20.dev</title>
    <link>https://jen20.dev/tags/vault/</link>
    <description>Recent content in Vault on jen20.dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <managingEditor>hello@jen20.com (James Nugent)</managingEditor>
    <webMaster>hello@jen20.com (James Nugent)</webMaster>
    <lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jen20.dev/tags/vault/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Nix Overlay for HashiCorp Tools</title>
      <link>https://jen20.dev/post/nix-hashicorp-tools-a-nix-overlay/</link>
      <pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><author>hello@jen20.com (James Nugent)</author>
      <guid>https://jen20.dev/post/nix-hashicorp-tools-a-nix-overlay/</guid>
      <description>&lt;p&gt;Infrastructure repositories tend to want an &lt;em&gt;exact&lt;/em&gt; version of tools. It&amp;rsquo;s desirable that when I work on Terraform code on my laptop, I use the same version as will be used in production, and the same version that my colleagues use. While I like to use Nix Flakes for per-project development environments, &lt;code&gt;nixpkgs&lt;/code&gt; is not much help here. It carries a single version of each of these tools — whichever one happened to be current when the package was last bumped — and it builds them from source. Both of those are the right defaults for a distribution and the wrong ones for pinning a team to &lt;code&gt;terraform&lt;/code&gt; 1.9.8 specifically, verified against the checksum HashiCorp published for it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
