atmos
atlantis
atmos | atlantis | |
---|---|---|
8 | 121 | |
581 | 7,335 | |
6.4% | 1.6% | |
8.6 | 9.7 | |
1 day ago | about 21 hours ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
atmos
-
AWS Landing zone creation: manual or AWS Control Tower?
This is why we created atmos to make it easier to manage large multi-account architectures. As a result, our components are reusable across organizations, regardless of how many accounts and regions they operate, and we minimize the snowflakes. And we avoid code generation, which is hard to thoroughly test in an automated fashion. Without naming names, lots of tools for terraform rely on code generation, but I see it as an anti-pattern that should be avoided.
- How to manage terraform code for large projects?
-
Terraform | Take your Terraform skills to the next level!
sorry did not find anything advanced. A better tool to make terraform scaleable is https://atmos.tools
-
Terraform docs say longstanding deployments should not use workspaces. what are your thoughts?
Workspaces are incredibly practical, and we leveraging them at-scale with literally thousands of workspaces using atmos for terraform. There is so much FUD around workspaces that is either ill-informed or based on outdated information. Any company using terraform at scale will rely on tooling and conventions. It's up to that tooling to ensure you are using terraform safely. Atmos is one of those tools. I'm not saying that you have to use workspaces, but just that there's nothing wrong with workspaces themselves.
-
List of most useful Terraform open-source tools
Check out atmos for a fresh take at managing terraform configurations and terraform workflows. Instead of managing HCL `.tfvar` files manually for configuration, it uses YAML, and supports concepts of imports (via deep merging), remote imports (anything supported by gogetter), mixins, inheritance, multiple-inheritance, vendoring of root modules, workflows, task runners (via custom subcommands), and much more. There's a bit of a learning curve and mind-shift required if coming from a Terragrunt background, but the experience is mindblowing after switching to it. Also, it's not limited to terraform.
-
Why does Hashicorp advise against using workspaces to manage environments?
We obviously don't have a project for your exact use case, but we have an open-source example repo that shows a fairly advanced scenario of using the Terraform Spacelift Provider https://github.com/spacelift-io/demo-preview-environments-manager, a simple quickstart of using it https://github.com/spacelift-io/terraform-starter and you can also see the CloudPosse Atmos project, for a very advanced scenario which generates lot's of Stacks based on your component specifications https://github.com/cloudposse/atmos.
- Atmos
- Atmos: Universal Tool for DevOps and Cloud Automation (Terraform, Helm, etc.)
atlantis
-
OpenTofu 1.7.0 is out with State Encryption, Dynamic Provider-defined Functions
None of these are a replacement of Terraform Cloud (recently rebranded to HCP Terraform). For example, when you create a PR, it could affect multiple workspaces. The new experimental version of TFC/TFE (I refuse to call it HCP!) implements Stacks, which is something like a workflow, and links one workspace output to other workspace inputs. None of the open-source solutions, including the paid Digger [0], support this - only the paid one, such as Spacelift [1] (which is the closest to TFC if you ask me). Having a monorepo of Terraform is a common design pattern, so, if I change an embedded module, it could trigger changes it many workspaces. As far as I know, Atlantis [2] can't really help in this case.
By the way, the reason I singled-out Spacelift is due to its quality, and the great Terraform provider it has. Scalr [3], for example, has a really low-quality Terraform provider. I extensively use the hashicorp/tfe provider to manage TFC itself.
[0]: https://digger.dev/
[1]: https://spacelift.io/
[2]: https://www.runatlantis.io/
[3]: https://www.scalr.com/
-
Terramate meets Atlantis 🚀
Atlantis is a pull request automation tool that works well with plain Terraform right away. But what if we're already using Terramate to generate Terraform code?
-
Top Terraform Tools to Know in 2024
Atlantis automates reviewing and deploying Terraform via pull requests, streamlining collaboration and ensuring consistency across Terraform deployments.
-
Stop Squinting at IaC Templates: Preview Diffs for Argo CD, Terraform, and more!
For example, Atlantisgo for Terraform, Zapier’s Kubechecks for Argo CD, Quizlet’s GitHub action all do something similar to this. But a generic, extensible tool for IaC providers doesn’t seem to exist. Additionally, many of them require exposing your Kubernetes cluster or other infrastructure to third-party access, webhooks, etc.
-
Self-service infrastructure as code
Our first attempt was to introduce other engineering teams to Terraform - the Platform team was already using it extensively with Terragrunt, and using Atlantis to automate plan and apply operations in a Git flow to ensure infrastructure was consistent. We'd written modules, with documentation, and an engineer would simply need to raise a PR to use the module and provide the right values, and Atlantis (once the PR was approved by Platform) would go ahead and set it up for them.
-
Seamless Cloud Infrastructure: Integrating Terragrunt and Terraform with AWS
Alternatively, you can look at solutions like Atlantis or spacelift.
-
What is the equivalent of docker-compose for terraform?
Atlantis: https://www.runatlantis.io/
-
Version of terraform binary cli does it include in the container
Looking at the commits at https://github.com/runatlantis/atlantis, it looks like 1.6.5. Am I right?
-
Terraform Cloud Pricing Changes Sticker Shock
We use Atlantis [0] for CI/CD automation of Terraform pull requests to a centralized repository. It's pretty good too, especially for a self-hosted solution. I can't see how Terraform Cloud's costs would be justifiable for us without a custom contract.
[0] https://www.runatlantis.io/
- Atlantis claims exemption from new HashiCorp license
What are some alternatives?
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
terraform-github-actions - Terraform GitHub Actions
terramate - Terramate CLI is an open-source Infrastructure as Code (IaC) orchestration tool for Terraform, OpenTofu, Terragrunt, Kubernetes, Pulumi, Cloud Formation, CDK, Azure Resource Manager (ARM), and others.
argo-cd - Declarative Continuous Deployment for Kubernetes
terraform-starter - Starter repository to play with Spacelift
backstage - Backstage is an open platform for building developer portals
demo-preview-environments-manager
akk-stack - Containerized EverQuest Emulator Server Environment
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
ops-examples - A repository of basic and advanced examples using Ops
tfsec - Security scanner for your Terraform code [Moved to: https://github.com/aquasecurity/tfsec]