Terraform

Terraform describes infrastructure resources in configuration files and uses providers to manage them. I use it in the DigiPulse infrastructure to make service configuration easier to review and reproduce.

Configuration and plans

The Docker provider connects Terraform to Docker resources. Shared configuration can describe similar environments with different input variables. Each environment needs its own plan based on its current state; a saved plan is not a reusable template for another environment.

Workspaces and sensitive data

CLI workspaces separate state, but are not an access-control boundary. State and plan files can contain secrets even when values are marked sensitive. Separate credentials, protected state storage and appropriate access controls are needed where environments require stronger isolation.

Infrastructure and application releases

I use infrastructure configuration to document resources and their relationships. Application releases can then follow their own CI/CD process. Terraform helps detect differences between declared and actual resources when a plan runs; it does not continuously prevent manual changes. Reviewing the plan is essential before applying changes that may replace or remove a resource.