Home
pltf is a Kubernetes-native CLI that transforms spec-driven intents into ready-to-run Terraform workspaces. Define stacks, environments, and services once, let pltf wire providers/backends/Helm charts, and run the host terraform binary so your deployments stay portable but repeatable.
flowchart TB
svc[(service.yaml)]
subgraph PROD[Production Env]
prod_service[Service A]
end
subgraph STAGE[Staging Env]
stage_service[Service A]
end
env[(env.yaml)]
svc --> prod_service
svc --> stage_service
prod_service --> env
stage_service --> env
Why teams rely on pltf
- Kubernetes-native workflows – embed EKS, Helm charts, and Kubernetes modules while Terraform manages state and providers.
- Spec-first operations – YAML specs capture backend, stacks, variables, and secrets instead of replicating Terraform code per env.
- Image + Terraform caching – Docker images build through Dagger with shared caches; Terraform runs natively with provider reuse.
- Custom modules welcome – register built-in modules by
typeor point to git repos viasource(HTTP/SSH) without a globalmodules_root. - Security + cost guardrails – tfsec/Infracost/Rover run with every Terraform plan and stream both timings and problem lists.