Pinned Tweet
Big update 🚀: v0.34.0: TerraDart CLI + AWS provider
init → typed Dart Stack → validate/plan
- No engine to install (managed OpenTofu)
- On Terraform? --engine terraform
- dev/stg/prd, typed #Flutter outputs
AWS: all of hashicorp/aws in @dart_lang
@FlutterDev
TerraDart supports Google Cloud, AWS, Cloudflare, and Appwrite today.
Azure is next.
If your Dart or Flutter team runs on Azure, tell us what you'd want to define first on the issue: github.com/nozomi-koborinai/…
Grateful to see TerraDart written about like this 🙏
What I keep coming back to is the full-stack Dart experience: infra and app in one language, with types holding them together.
Still early, and I'll keep pushing on it.
Than you, Thiago Magalhães.
medium.com/@thiago.sarmento_…
The AWS provider: all of hashicorp/aws as typed Dart. Pick it in terradart init, with a region per environment.
terradart.dev/docs/providers…
GitHub: github.com/nozomi-koborinai/…
Install: dart pub global activate terradart_cli
AWS is coming...
TerraDart isn’t a thin wrapper. Typed AWS in Dart, same language as your Flutter app. Terraform still does the apply.
Plus a DX jump for full-stack Dart. Infra values into the app without the glue tax. Landing soon.
terradart-migrate is in 0.28.
One command turns existing Terraform HCL into typed Dart Stacks. Unmigrated bits keep running as Terraform — adopt resource by resource, no big-bang rewrite.
brew install nozomi-koborinai/tap/terradart-migrate
terradart.dev/docs/migrate-f…
TerraDart: type-safe IaC for Dart.
Terraform stays the apply layer. You author cloud resources in Dart, emit standard *.tf.json, and keep the plan/apply pipeline you already run.
terradart.dev

