3 ms·
Almost exactly a year ago we have launched Digger. Since then thousands of developers started using it, and our mission remains to build the best developer plat
by igorzij 4y ago
Almost exactly a year ago we have launched Digger. Since then thousands of developers started using it, and our mission remains to build the best developer platform ever.
But we are often asked - why so many products that look so similar? After Digger we have also launched Lemon, Alicorn and most recently AWS Bootstrap to name a few. The answer is simple: we want every feature of Digger to be best-in-class. So we are making a product out of it and launch it and perfect it if people need it, or kill the feature if there is not enough demand.
Terraform generation is one of the most powerful features of the platform. Not only your AWS account is taken care of - you also get the underlying code that is fully customisable. So you are not limited by the UI and can literally build whatever you want as long as AWS supports it. It's easy with Terragen:
1. Connect your AWS account
2. Connect a GitHub repository for your infrastructure code
3. Terragen will push generated Terraform there
4. Then you can add more apps and services - and Terraform will get automatically updated!
5. And you can use the digger_overrides folder to add your own custom terraform
We believe that the only way to make a truly great platform is to listen to the users and ship things they need. Tell us what you think!
PS - we have also launched on ProductHunt today: https://www.producthunt.com/posts/terraform-generator-by-digger https://www.producthunt.com/posts/terraform-generator-by-dig...
- cube2222 4y agoI'm not sure if I understand your tool correctly. Do you generate Terraform code based on the AWS account, to help with a migration to Terraform? Or is it that your platform works in that it "compiles" whatever is created in it to Terraform, to be run by the user on their AWS account? In other words, it's kind of a GUI DSL for Terraform?
- igorzij 4y agoThe latter, yes. The former is a feature on the roadmap. Our idea is to make it as easy as possible for the user to take advantage of IaC without having to learn it. Remove the entry barrier, give a nice UI that would make it super easy to do the basic stuff, which is like 90% of what's needed on a day-to-day basis. For the remaining 10% the user has full control over underlying Terraform. So you can customise only the parts that need to be custom; that's much easier than starting from scratch.
- dmead 4y agodo you care about terragrunt support? can i package up the terraform that gets produced and put it in a terragrunt module? my stuff uses terragrunt extensively. it would be really cool if this fit together nicely.
- igorzij 4y agothat's a great point indeed - we have Terragrunt support on the roadmap but didn't manage to ship yet. What kind of stuff if you don't mind sharing?
- dmead 4y agoI work on cloud infra in a healthcare setting. Basically a combination of on and off prem kubernetes (so multiple instances of the k8s provider) and other resources from the gcp and aws providers. Really what a codegen would want to do in this case would be to make a terragrunt.hcl file that would make the accompanying terraform files callable. It really wouldn't nessesitiate anything else unless you want to make it easy to parameterize values per CI environment. Then you want multiple terragrunt.hcls
- httgp 4y agoDoes this only generate HCL, or does it support CDKTF/TypeScript too?