aztfy
atmos
aztfy | atmos | |
---|---|---|
19 | 8 | |
1,034 | 574 | |
- | 5.2% | |
9.6 | 8.6 | |
about 1 year ago | 5 days ago | |
Go | Go | |
Mozilla Public License 2.0 | 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.
aztfy
-
Terraform Tips & Tricks: Managing Large-Scale Azure Resource Imports
Aztfy is a tool developed by Microsoft that allows you to bulk import resources, it has some configuration so you can specify what to import, the names to import and so on. After spending some time with the tool, I quickly realized it may be a no-go. The problem I had with this tool is twofold:
-
Azure Terrafy: Import and Manage Existing Azure Resources with Terraform
Azure Terrafy is a tool that makes it easy to import your existing Azure resources into Terraform modules. Suppose you're an Azure user looking to manage your infrastructure with the power of Terraform. In that case, Azure Terrafy can save you time and effort by automating the process of incorporating your existing resources into your Terraform configuration. This is especially useful for those who have a "brownfield" environment, where their infrastructure already has a number of existing resources that need to be brought under the management of Terraform. It can save you a lot of time and effort. Without Terrafy, you would need to manually create a Terraform configuration file for each resource you want to manage. This can be tedious and error-prone, especially if you have many resources.
-
terraforming existing infra
If that existing infrastructure happens to be in Azure, look into aztfy, it's helped me build some structures to replace first-generation hand-deployed resources.
-
Open Source Terraform projects - azure focused (open to other providers as well)
Azure Terrafy
-
How do I use TF only for new stuff in Azure (leave stuff, that was created in the portal before, like it was)?
https://github.com/Azure/aztfy I've done this, as the guy above says it's all flat but perfectly readable.
-
List of most useful Terraform open-source tools
Aztfy (Azure only): https://github.com/Azure/aztfy
Basic GitOps:Atlantis - https://www.runatlantis.io/
DRY wrapper:
"Reverse"/creating from existing cloud resources:Terraformer: https://github.com/GoogleCloudPlatform/terraformerAztfy (Azure only): https://github.com/Azure/aztfy
- Aztfy
- My tfstate got messed up and my most recent correct backup is incomplete. How do I get terraform to recursively add Azure RGs and their resources?
- converting existing infrastructure using azure functions from the arm template into terraform
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.)
What are some alternatives?
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
aztfmove - Simple tool to move Azure resources based on Terraform state
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.
terrascan - Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure.
terraform-starter - Starter repository to play with Spacelift
aztfexport - A tool to bring existing Azure resources under Terraform's management
demo-preview-environments-manager
terrascan - Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure. [Moved to: https://github.com/accurics/terrascan]
akk-stack - Containerized EverQuest Emulator Server Environment
terraforming - Export existing AWS resources to Terraform style (tf, tfstate) / No longer actively maintained
ops-examples - A repository of basic and advanced examples using Ops