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.<p>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.<p>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:<p>1. Connect your AWS account<p>2. Connect a GitHub repository for your infrastructure code<p>3. Terragen will push generated Terraform there<p>4. Then you can add more apps and services - and Terraform will get automatically updated!<p>5. And you can use the digger_overrides folder to add your own custom terraform<p>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!<p>PS - we have also launched on ProductHunt today: <a href="https://www.producthunt.com/posts/terraform-generator-by-digger" rel="nofollow">https://www.producthunt.com/posts/terraform-generator-by-dig...</a>
Unfortunate name collision with the established (and still actively developed) 3D landscape renderer [1].<p>[1] <a href="https://planetside.co.uk/" rel="nofollow">https://planetside.co.uk/</a>
What do you call "resource"? I went directly to the pricing page (btw on my small 11" laptop screen the logo left overlaps the menu) and for the hobbyist it says one service and one resource - what is that "one resource"? One S3 bucket? Then it's useless to me - as hobbyist as I was - and I'd have to pay 200$/month (next plan is 50$/mo and minimum 4 users). I won't pay that much for my hobby projects. Or maybe you call "resource" something else, like one repo? I have my hobby projects in more than one repo, so again I wouldn't qualify for hobbyist pricing...
This project seems to wholesale ignore "terraform modules" in it's claims about reusability and modularity. Most of the problems it solves are already solved.<p>The description and marketing are very mixed. It generates bespoke Terraform based on... vague descriptions? "Give me a postgres DB" seems to be the level of input from what I can tell. It then goes off to create one and give you the TF it used? I was really hoping this was "automatically generate Terraform FROM AWS" to import existing resources.<p>This sounds like the SaaS-ified version of Gruntwork.io, where they give you best practices templates and leave it up to you to fill in the particulars.
That's great stuff! We have exporter functionality in the Databricks Terraform provider [1] and a lot of customers started to use Terraform for existing Databricks resources because they don't need to re-implement everything manually - just point to workspace, and wait few minutes.<p>[1] <a href="https://registry.terraform.io/providers/databrickslabs/databricks/latest/docs/guides/experimental-exporter" rel="nofollow">https://registry.terraform.io/providers/databrickslabs/datab...</a>
Im gonna hide that from my manager or he will fire me.<p>They would love to sack some devops to replace them with juniors clicking stuff in UI.<p>Sooner or later real experts will be pushed out through SaaS solutions but overall the quality of solutions prepared will be crap.<p>I can already compare for example Datadog to our own dedicated Monitoring stack. Managers would never again allow us to build it, despite it being 10x better than generic solution.
Increasingly it seems like people think there is a need for tools that bridge the gap between simple and complicated IaC. I think this is a better idea than a bespoke cli tool that does something similar[1], but I don't think it escapes the core problems that tool has, which are the same problems that people and organizations encounter with other complicated infrastructure/deployment tooling: getting good at these things is a time sink, and shortcuts that magic away some of the pain also magic away the ability to learn.<p>[1] <a href="https://github.com/nathants/libaws" rel="nofollow">https://github.com/nathants/libaws</a>
At first I was going to complain that the whole "what we actually do" spiel was tiny and hidden away up the top there, but after clicking it think you have really well written docs that explained it well.<p>Looks decent. Good luck.
Oh man, was excited to try this but then was prompted to login. Why do I need to sign in with my GitHub? Why can’t I just generate terraform like you claim? Why do I have to give you personal details to do so?
Terragen is already the name of a 3D terrain generator/renderer. <a href="https://en.m.wikipedia.org/wiki/Terragen" rel="nofollow">https://en.m.wikipedia.org/wiki/Terragen</a><p>I’m pretty sure your company can be sued for trademark infringement.
Without having the ability to try right now, so excuse the ignorance, are you setting up and creating terraform configs and then running them against aws or do we get the configs after generation?