Guide
GuidesPlain English to Terraform: how it works
Plain English to Terraform
Describing infrastructure in a sentence and getting back real Terraform is no longer a demo trick. Here is how it works in practice, what the generated code looks like, and where it holds up under an enterprise security review.
~3 min read
Why hand-writing Terraform is the bottleneck
Infrastructure as code is the right model: every group, policy, and integration lives in version control, reviewed and reproducible. The slow part is the writing. Correct Terraform across identity, cloud, and device providers means knowing the exact resource names, the required arguments, and the quirks that the docs gloss over. Most teams either staff a dedicated platform engineer or let the IaC coverage quietly fall behind reality.
Generating Terraform from a description
The workflow is simple on the surface. You write what you want in plain English: a new Okta group with single sign-on into three apps, a Jamf policy that enforces FileVault, a scheduled function that sweeps stale users. Trueform reads that description and writes the Terraform to match. The result is standard HCL you own, not a proprietary abstraction you rent.
The difference between a toy and a tool is the glue. Real environments connect providers: an Okta event hook that calls a Lambda, a GCP Cloud Function triggered by an identity event, Jamf and Fleet managed through GitOps. Trueform writes those connections, merges provider blocks, and dedupes variables so the output applies as one clean module instead of a pile of disconnected snippets.
What you get back: real HCL, not a wrapper
Every generation produces files you can read, diff, and apply yourself. One click opens a pull request in your GitHub repo, or saves a ZIP. Each module ships with an apply runbook that documents the provider quirks it encodes, so the plan is self-explaining when a reviewer opens it. Nothing is locked behind a platform: if you stop using Trueform tomorrow, the Terraform keeps working.
Seven providers, one module
Trueform covers Okta, AWS, GCP, JAMF, Fleet, Snowflake, and Kandji. The provider quirks it encodes, the Jamf parallelism limits, the Fleet GitOps workflow, the Okta event hooks, come from running these systems in production. That is the same operator experience behind everything Auxon does. For the identity side specifically, see our guide on Okta Terraform automation, or the Trueform product page for the full picture.
Related guides
Keep reading
Identity
Okta Terraform automation
Managing Okta as code: what belongs in Terraform, the parts that bite (event hooks, drift, lifecycle), and how to get it right.
Governance
IT governance, run by agents
How Paragon turns governance from a dashboard of problems into an assess, generate, remediate loop across twelve modules.
See it on your own stack
Tell us the providers you run and we will generate a module against them live.
Subscribe
Get new guides when they drop. One email when there is something to read; never spam.