<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Eso on ferkakta.dev</title><link>https://ferkakta.dev/tags/eso/</link><description>Recent content in Eso on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Wed, 25 Mar 2026 21:00:00 -0500</lastBuildDate><atom:link href="https://ferkakta.dev/tags/eso/index.xml" rel="self" type="application/rss+xml"/><item><title>from feature_flags import *</title><link>https://ferkakta.dev/from-feature-flags-import-star/</link><pubDate>Wed, 25 Mar 2026 21:00:00 -0500</pubDate><guid>https://ferkakta.dev/from-feature-flags-import-star/</guid><description>&lt;p&gt;A colleague needed a feature flag enabled on one tenant. &lt;code&gt;FEATURE_FLAG_ENABLE_AGENTS=True&lt;/code&gt; — one environment variable, one pod. I added it to the K8s secret manually, restarted the pod, and he was unblocked in two minutes.&lt;/p&gt;
&lt;p&gt;Then I realized: the next terraform apply would overwrite that secret without the flag. The ExternalSecret syncs from SSM, and the flag wasn&amp;rsquo;t in SSM through any path terraform knew about. My manual fix had a shelf life of one deploy.&lt;/p&gt;</description></item></channel></rss>