Secrets Management
Secrets need a tested lifecycle: creation, rotation, revocation, and expiration, including enforcement at the protected service.
-
-
Infrastructure and Configuration as Code
Your code says what should exist. The state file says what the tool believes exists. The cloud knows what actually exists. Three answers, one system.
-
Infrastructure as Code: State and Drift
Infrastructure code is only half of the system; the tool also keeps a record of what it created. This guide explains state, plans, locks, drift, secrets, tests, and rollback, with Terraform examples and the output of local runs.