<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets Management on Terraform Pilot</title><link>https://www.terraformpilot.com/tags/secrets-management/</link><description>Recent content in Secrets Management on Terraform Pilot</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Sun, 12 Apr 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://www.terraformpilot.com/tags/secrets-management/feed.xml" rel="self" type="application/rss+xml"/><item><title>Terraform Ephemeral Resources Explained: Temporary Values for Secrets and Tokens</title><link>https://www.terraformpilot.com/articles/terraform-ephemeral-resources-explained/</link><pubDate>Sun, 12 Apr 2026 10:00:00 +0000</pubDate><guid>https://www.terraformpilot.com/articles/terraform-ephemeral-resources-explained/</guid><description>Ephemeral resources are a newer Terraform feature (announced at HashiDays 2025) that solves a long-standing problem: how to use secrets during a Terraform run without storing them in state. Database passwords, API tokens, session credentials — values you need during apply but don&amp;rsquo;t want persisted anywhere.
The Problem With regular resources and data sources, everything goes into state:
# ❌ This stores the password in terraform.tfstate! resource &amp;#34;random_password&amp;#34; &amp;#34;db&amp;#34; { length = 32 } # ❌ This stores the secret value in state too!</description></item></channel></rss>