Terraform sensitive Does Not Mean Secret
Marking a value sensitive redacts normal CLI and UI output. It does not remove that value from Terraform state or saved plan files.
secrets
Git, Runtime State and Secrets Need Different Jobs
Operational confusion falls when desired configuration, mutable data and confidential values stop competing to be one source of truth.
Deleting a Secret from the Current Git Tree Does Not Remove It from History
Production readiness has to treat leaked credentials as compromised even after the file disappears from the latest commit.
A Secret Manager Is an Authorization System, Not Just Encrypted .env
OpenBao adds identity, policy, versioning, leases and audit around secrets instead of merely moving plaintext to a different file.
Secrets Are the Part of a GitOps Repo I Do Not Want to “Just Add”
How to think about credentials when application manifests are intentionally stored in Git.
Secrets Are Part of Disaster Recovery Even When They Are Correctly Missing from Git
Separating secrets from source control creates a recovery dependency that must be documented and tested.
Notification Authentication Belongs Outside Git
Moving alert delivery to authenticated self-hosted ntfy introduced a publisher token that the alert-sink needs at runtime.
Backend-Delivered SIP Configuration Keeps Secrets Out of Factory Images
Per-device PBX credentials should be provisioned after identity is established, not cloned into every unit.
Deep Database Collection Did Not Need Copied Passwords
Copying every application database password into the observability stack would have expanded the secret blast radius just to collect metrics.
Terraform Ephemeral Values and Write-Only Arguments Change the Secret-Handling Model
Terraform 1.10+ ephemeral values and 1.11+ write-only arguments let temporary values pass through a run without being persisted in state or plan artifacts when providers support them.
Traverse-Only ACLs Are Useful When Secrets Live Under Root-Owned Trees
A service can be allowed through one protected directory without being allowed to inspect the directory itself.
Production Infrastructure Became Easier Once Git, Runtime State and Secrets Had Different Jobs
Most operational confusion came from mixing desired configuration, live state and credentials into the same place.