<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Age on Morgan Connors</title>
		<link>https://morganconnors.dev/tags/age/</link>
		<description>Recent content in Age on Morgan Connors</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 24 Jul 2026 00:36:10 -0400</lastBuildDate>
		
			<atom:link href="https://morganconnors.dev/tags/age/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>SOPS &amp; Age</title>
				<link>https://morganconnors.dev/posts/03-sops-age/</link>
				<pubDate>Fri, 24 Jul 2026 00:36:10 -0400</pubDate>
				<guid>https://morganconnors.dev/posts/03-sops-age/</guid>
				<description>&lt;p&gt;&lt;strong&gt;None of the keys shown here are actually used for anything other than this example.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Keeping Infrastructure as Code (IaC) files usually means also storing secrets to be used in these files. These secrets can&amp;rsquo;t just be stored in a git repo unencrypted like regular IaC files, that would be silly. So, how can we do it?&lt;/p&gt;&#xA;&lt;p&gt;With SOPS and Age.&lt;/p&gt;&#xA;&lt;p&gt;After using these two tools for the last couple of months, I have become quite comfortable with using them to script deployments requiring tokens, api keys, and other sercets.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
