terragrunt-infrastructure-live-example VS terrateam

In the official Terragrunt documentation there is a good article about how to set up a Terragrunt project and where to place modules. In fact, there is also a repository on GitHub providing an example project on how the creators recommend setting up Terragrunt. I certainly recommend going through that repository, because it is a good reference for a starting point. Having that said, I like to structure mine a little bit differently. My recommendation is to have different AWS accounts for each environment. Getting a new account usually is relatively easy to accomplish even if we are working in a corporate environment (your workplace most likely is using AWS Organizations to manage accounts). The existence of multiple accounts does not require additional costs, we only pay for what we use.

NOTE: More information about the terragrunt.hcl file can be found in this example repository.

Here's a pointer to an example repository with a Terragrunt monorepo (good, easy to manage), and each module called gets its unique statefile (good, smaller blast radius) where the tradeoff is learning a new tool and paradigm: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example.

I also highly recommend to check out how terragrunt recommends structuring your repo and even further details on this documentation page.

https://github.com/gruntwork-io/terragrunt-infrastructure-live-example/blob/master/_envcommon/mysql.hcl https://terragrunt.gruntwork.io/docs/features/keep-your-terraform-code-dry/

did you have a look at this example? https://github.com/gruntwork-io/terragrunt-infrastructure-live-example/blob/master/terragrunt.hcl

Terragrunt! Using a scaffolding approach like this for inspiration https://github.com/gruntwork-io/terragrunt-infrastructure-live-example

I would recommend taking a look at the example repo here: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example. The layout you have doesn't look like a structure that would work well with terragrunt.

A good example is in gruntwork-io / terragrunt-infrastructure-live-example repository and further documentation on Terragrunt's own documentation page.

Terrateam: After getting into some really big issues when running Terragrunt with Github Actions, I decided to look for a better CI solution. Terrateam is my CI/CD tool of choice here. Unfortunately as of December 2023, they increased their price from USD $175 to USD $496 monthly. Me being an existing customer I still pay the old amount (thank God!) Alternatively, you can look at solutions like Atlantis or spacelift.

Disclaimer: I am a co-founder of Terrateam (https://terrateam.io/) a competitor to Digger.

For anyone using Digger, are all of the enterprise features in the open source codebase? If you pay for digger, or you just paying for support and hosting? Or do they separate OSS from Community, Pro, and Enterprise plans?

Disclaimer: Co-founder of Terrateam.

For Terrateam[0], we have probably 70% of the enterprise offering but at around 1/10th the price. If there are any features that are deal breaker, feel free to reach out to me and we'll see what we can do. That being said, Spacelift is a much more luxurious piece of software than us. We are very utilitarian, but we have to rationalize that low price-point somehow.

[0] https://terrateam.io

Terrateam is an enterprise Atlantis alternative that lets you plan and apply all within pull requests and very minimal setup. We have a pretty active slack if you have any questions.

> It sure looks like AWS admin credentials are shared with Github, and also available to anything else in the diggerhq/digger action

I am a co-founder of Terrateam[0] which is a Terraform CI/CD as well. At the end of the day, you need to execute something to do these operations and having this component open source is important for auditing purposes. For Terrateam, we lean heavily into GitHub Actions so GitHub is at least managing any secrets and runs. One challenge is users could pin the Action that we publish to a specific version, but we also update it regularly and communicating to customers to update it is a challenge.

[0] https://terrateam.io

There are lots of options for this. I am co-founder of a product called Terrateam which makes it easy to slice up a mono repo for these usecases. We specialize in GitHub installations. But Spacelift, env0, and Scalr exist as options as well.

Many of the CI/CD tools take care of this. Terrateam tracks which plans are still valid after an apply and will force a re-plan. It also ensures that only one apply happens at a time.

We just released our self-hosted version available here: https://github.com/terrateamio/terrateam

I use Terrateam (disclaimer, I'm also a co-founder of it) does PR-level locks (but only on apply, or merge), and does apply serialization, and invalidates outdated plans on apply. You can plan as much as you want in parallel, though, because that does not impact the output. I don't think there are many other options for how to handle this.