aztfy
terraforming
aztfy | terraforming | |
---|---|---|
19 | 9 | |
1,034 | 4,298 | |
- | - | |
9.6 | 1.6 | |
about 1 year ago | over 2 years ago | |
Go | Ruby | |
Mozilla Public License 2.0 | MIT License |
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
terraforming
- Importing multiple modules at once from AWS
-
Tools like terraformer
Terraforming
- Copy Azure resources via terraform
- Existing AWS resource to HCL?
-
Where to start with a mess?
I would also strongly recommend an iterative triage process: don't feel that you need to solve everything all once. It's a huge amount of progress if you can get to a stage where you understand the relationships between services, have enough monitoring to identify failures, and can iteratively move services to more granular IAM policies even if it's all still running in one big account. Simply using a tool like terraformer or terraforming to move the manual configuration into an IaC workflow is an accomplishment, especially since it helps you both make changes more confidently and identify where new changes are still being made. Depending on the politics, that last part might be important: you'll be unpopular if you take away everyone's rights but you'll probably have better luck first nudging people to make them using a sensible flow rather than by hand.
-
Just starting out with terraform. Doubts wrt existing infra.
Haven't tried this but if I ever find myself in your situation I'll give it a spin https://github.com/dtan4/terraforming
-
Continuous Infrastructure Deployment with Terraform Cloud
There are a couple of tools to automate creating terraform configuration and prepopulate state from existing resources, like terraforming, terraformer or cf-terraforming. But it is still cumbersome and laborious and in my experience, it's usually way easier to just recreate everything within terraform from scratch wherever that's possible.
- Current infrastructure as code
-
DevOps tools you should have on your belt
🧪 Terraforming export existing AWS resources to Terraform style (tf, tfstate).
What are some alternatives?
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
aztfmove - Simple tool to move Azure resources based on Terraform state
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
terrascan - Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure.
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
aztfexport - A tool to bring existing Azure resources under Terraform's management
cf-terraforming - A command line utility to facilitate terraforming your existing Cloudflare resources.
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]
aws-toolkit-vscode - Amazon Q, CodeWhisperer, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
terratag - Terratag is a CLI tool that enables users of Terraform to automatically create and maintain tags across their entire set of AWS, Azure, and GCP resources
saml2aws - CLI tool which enables you to login and retrieve AWS temporary credentials using a SAML IDP