terrateam
terrateam | multi-cloud-terragrunt-filesystem | |
---|---|---|
12 | 3 | |
95 | 8 | |
- | - | |
4.5 | 6.9 | |
about 2 months ago | 10 months ago | |
HCL | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terrateam
-
Seamless Cloud Infrastructure: Integrating Terragrunt and Terraform with AWS
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.
-
Digger – an open-source IaC automation and collaboration software
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?
-
Terraform best practices for reliability at any scale
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
-
Terraform Tower
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.
-
Show HN: Digger – an Open Source Terraform automation and collaboration tool
> 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
-
Multi-cloud/ Multi-region Terraform deployment in Github
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.
-
Do you run terraform apply before or after a merging?
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.
-
Terrateam: Atlantis-style Terraform pull request automation
We just released our self-hosted version available here: https://github.com/terrateamio/terrateam
-
How do you handle race condition while sharing state remotely with your team, eg - concurrent apply, or plan during apply?
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.
- Terrateam Self-Hosted
multi-cloud-terragrunt-filesystem
- Multi-cloud/ Multi-region Terraform deployment in Github
-
Is it safe to commit a Terraform file to GitHub?
I'm not sure about project_id being a sensitive value. Account IDs are not officially considered sensitive in AWS circles, but most people still treat them that way. I checked mine in before for the only GCP thing I ever did, https://github.com/iangrunt/multi-cloud-terragrunt-filesystem/blob/main/gcp/sre-projects/project-delta/project.hcl. This would be considered a "root module" (it's not) where that would be a private repo anyways, so checking in account IDs would be fine. That being said, it is still possible to write root modules and use the context of your pipelines to get these kinds of values more safely.
-
Collection of "fake" AWS & GCP Terraform modules for learning and testing
Here's an example repo where I use those modules, https://github.com/iangrunt/multi-cloud-terragrunt-filesystem/tree/main.
What are some alternatives?
digger - Digger is an open source IaC orchestration tool. Digger allows you to run IaC in your existing CI pipeline ⚡️
terraform-fake-modules
branch-deploy - Enabling Branch Deployments through IssueOps with GitHub Actions - If you find this project useful, give it a star! ⭐️
otf - An open source alternative to terraform enterprise.
sops - Simple and flexible tool for managing secrets
terrakube - Open source IaC Automation and Collaboration Software.
git-crypt - Transparent file encryption in git
dagger - Application Delivery as Code that Runs Anywhere
atlantis - Terraform Pull Request Automation
terraform-aws-bootstrap - Setup Terraform remote state in the S3 backend (with DynamoDB locking) for AWS