<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Spelunk on Zio Ivan</title>
    <link>https://ivandemarino.me/tags/spelunk/</link>
    <description>Recent content in Spelunk on Zio Ivan</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>detronizator&#43;blog@gmail.com (Ivan De Marino, aka &#34;Zio Ivan&#34;, aka &#34;detro&#34;)</managingEditor>
    <webMaster>detronizator&#43;blog@gmail.com (Ivan De Marino, aka &#34;Zio Ivan&#34;, aka &#34;detro&#34;)</webMaster>
    <copyright>2004-2026 Ivan De Marino. Licensed under CC BY 4.0</copyright>
    <lastBuildDate>Sun, 30 Aug 2026 22:03:00 +0000</lastBuildDate>
    <atom:link href="https://ivandemarino.me/tags/spelunk/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Spelunk v2.2: now with CLI</title>
      <link>https://ivandemarino.me/posts/spelunk-2-2-cli/</link>
      <pubDate>Sun, 30 Aug 2026 22:03:00 +0000</pubDate><author>detronizator&#43;blog@gmail.com (Ivan De Marino, aka &#34;Zio Ivan&#34;, aka &#34;detro&#34;)</author>
      <guid>https://ivandemarino.me/posts/spelunk-2-2-cli/</guid>
      <description>&lt;p&gt;Quick recap for those joining late. &lt;a href=&#34;https://github.com/detro/spelunk&#34;&gt;Spelunk&lt;/a&gt; started as
a Go library to fetch secrets from any &lt;a href=&#34;https://github.com/detro/spelunk#sources-secretsource&#34;&gt;Source&lt;/a&gt; using a URI-like &lt;a href=&#34;https://github.com/detro/spelunk#coordinates-secretcoord&#34;&gt;Coordinates&lt;/a&gt; system (&lt;a href=&#34;https://ivandemarino.me/posts/you-need-spelunk/&#34;&gt;intro&lt;/a&gt;). Then I added support for various cloud Secret Managers and a heap of &lt;a href=&#34;https://github.com/detro/spelunk#modifiers-secretmodifier&#34;&gt;Modifiers&lt;/a&gt; (&lt;a href=&#34;https://ivandemarino.me/posts/spelunk-1-2-and-1-3/&#34;&gt;&lt;code&gt;v1.2.0&lt;/code&gt; + &lt;code&gt;v1.3.0&lt;/code&gt;&lt;/a&gt;). And after that I tore the repo apart into isolated modules/plugins, so you would only compile the third-party SDKs you actually needed (&lt;a href=&#34;https://ivandemarino.me/posts/spelunk-2/&#34;&gt;&lt;code&gt;v2.0.0&lt;/code&gt;&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;And now, time to tick another box!&lt;/p&gt;
&lt;h2 id=&#34;spelunk-is-a-cli-now-&#34;&gt;Spelunk is a CLI now 💲&lt;/h2&gt;
&lt;p&gt;I ended &lt;a href=&#34;https://ivandemarino.me/posts/you-need-spelunk/&#34;&gt;the very first post&lt;/a&gt; with a little TODO list, and one of the points was: &lt;em&gt;&amp;ldquo;Build a &lt;code&gt;spelunk&lt;/code&gt; binary, so to embed it in shell scripts&amp;rdquo;&lt;/em&gt;. That&amp;rsquo;s
what &lt;a href=&#34;https://github.com/detro/spelunk/releases/tag/v2.2.1&#34;&gt;&lt;code&gt;v2.2.*&lt;/code&gt;&lt;/a&gt; is about:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spelunk v2.0.0 - The Multi-Module &amp; Lean-Dependencies Release</title>
      <link>https://ivandemarino.me/posts/spelunk-2/</link>
      <pubDate>Fri, 29 May 2026 17:00:00 +0000</pubDate><author>detronizator&#43;blog@gmail.com (Ivan De Marino, aka &#34;Zio Ivan&#34;, aka &#34;detro&#34;)</author>
      <guid>https://ivandemarino.me/posts/spelunk-2/</guid>
      <description>&lt;p&gt;I just released &lt;strong&gt;Spelunk &lt;code&gt;v2.0.0&lt;/code&gt;&lt;/strong&gt;, a major architectural redesign of the library
to dig up secrets from various sources, for Golang.&lt;/p&gt;
&lt;p&gt;If you have read &lt;a href=&#34;https://detro.github.io/tags/spelunk/&#34;&gt;previous posts about Spelunk&lt;/a&gt;,
you know that the project started with a simple mission: to provide a single, clean, URI-based interface (&lt;code&gt;scheme://location?modifier=arg&lt;/code&gt;) to fetch secrets across any
storage backend—whether it is local files, environment variables, Kubernetes, HashiCorp Vault, AWS, Azure, or GCP.&lt;/p&gt;
&lt;p&gt;With &lt;code&gt;v2.0.0&lt;/code&gt;, I have re-designed Spelunk to solve dependency bloat and make
the core library exceptionally lean.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spelunk v1.2.0 &#43; v1.3.0: Secret Managers and Extractors</title>
      <link>https://ivandemarino.me/posts/spelunk-1-2-and-1-3/</link>
      <pubDate>Tue, 17 Mar 2026 12:00:00 +0000</pubDate><author>detronizator&#43;blog@gmail.com (Ivan De Marino, aka &#34;Zio Ivan&#34;, aka &#34;detro&#34;)</author>
      <guid>https://ivandemarino.me/posts/spelunk-1-2-and-1-3/</guid>
      <description>&lt;p&gt;If you read my &lt;a href=&#34;https://ivandemarino.me/posts/you-need-spelunk/&#34;&gt;previous post introducing Spelunk&lt;/a&gt;, you already know: fetching secret from any source should be easy, especially for your users.
Reading them from HashiCorp Vault, Kubernetes or whatever should be easy to.
If they where JSON objects, extracting specific fields should be easy.
Switching between a secret providers should (repeat with me!) &lt;em&gt;easy&lt;/em&gt;!&lt;/p&gt;
&lt;p&gt;Well, since the initial announcement, my pickaxe has been swinging non-stop in the Spelunk caves, and I unearthed two updates: &lt;strong&gt;v1.2.0&lt;/strong&gt; and &lt;strong&gt;v1.3.0&lt;/strong&gt;! 🎉&lt;/p&gt;</description>
    </item>
    <item>
      <title>Digging-up Secrets? You need Spelunk!</title>
      <link>https://ivandemarino.me/posts/you-need-spelunk/</link>
      <pubDate>Sat, 07 Mar 2026 20:28:00 +0000</pubDate><author>detronizator&#43;blog@gmail.com (Ivan De Marino, aka &#34;Zio Ivan&#34;, aka &#34;detro&#34;)</author>
      <guid>https://ivandemarino.me/posts/you-need-spelunk/</guid>
      <description>&lt;p&gt;If your Team, Organization or Company is serious about where to keep credentials used by services (or to interact with them), they are likely in &lt;a href=&#34;https://kubernetes.io/docs/concepts/configuration/secret/&#34;&gt;Kubernetes Secrets&lt;/a&gt;, &lt;a href=&#34;https://developer.hashicorp.com/vault/docs/secrets/kv&#34;&gt;Hashicorp Vault&lt;/a&gt;, &lt;a href=&#34;https://cloud.google.com/security/products/secret-manager&#34;&gt;one&lt;/a&gt; &lt;a href=&#34;https://aws.amazon.com/secrets-manager/&#34;&gt;of the various&lt;/a&gt; &lt;a href=&#34;https://azure.microsoft.com/en-us/products/key-vault&#34;&gt;cloud-based&lt;/a&gt; Secrets Managers, &lt;a href=&#34;https://developer.1password.com/&#34;&gt;1Password&lt;/a&gt;, etc. Then, when running locally, they might be in your Environment Variables, in a &lt;code&gt;.env&lt;/code&gt;, in a file or just in plaintext in a script (naughty!).&lt;/p&gt;
&lt;p&gt;This might lead to services and tools written to deal with those different “secret provision scenarios”. Or tricky/brittle local setups.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
