I'm back with another side project. This time with a CLI written in python that can aid you in converting Cloudformation Templates to Terraform. It can do about 70% of the work for you and I hope to further improve this percentage if there is interest from the community.
Could you elaborate why one would want to do this besides for unifying everything to terraform.
If you have already written cloudformation, you’d be losing a stack view which centrally describes things deployed in that AWS ac and how they are inter-related?
I actually thought your comments on having centrally described infrastructure pretty deserving of its own reply.
Because switching to Terraform doesn't mean you would lose this capability. It just moves it from the AWS console to your code repository. Correctly written Terraform code will show what is deployed in AWS and how it's inter-related.
Unfortunately while Terraform is an IaC tool, it will allow you to write non-IaC code. So if you have a Terraform root module, but you cant tell what's deployed where, because someone made the AWS creds a variable instead of hard coded... That's not real IaC.
I'm back with another side project. This time with a CLI written in python that can aid you in converting Cloudformation Templates to Terraform. It can do about 70% of the work for you and I hope to further improve this percentage if there is interest from the community.