> It's very hard because every providers have different APIs and concepts so you have to start from scratch for each.
Why not build it as a layer on top of Terraform?
> It's very hard because every providers have different APIs and concepts so you have to start from scratch for each.
Why not build it as a layer on top of Terraform?
Let's take an example: You have an architecture with a CI/CD. Great. You add your CodePipeline and CodeBuild ressources to your plan. Perfect.
For the CI part, you want your build to start on every commit on every non-master branch. Bad news: CodePipeline doesn't have support for multi-branch. So you will need to find a way to clone the default pipeline for each new branch.
Repeat this for all the user-friendly features (GitHub check runs, env vars management, deployment monitoring/rollback...) for the three cloud providers for all the different architectures and you start to feel the difficulty (I can testify ;)).
Users wouldn’t need to know about Terraform (unless they wanted to. It might be nice to have a way to export the Terraform code)
I use Terraform “under the hood” for this project.
What I was trying to explain is that the "hard part" is not the creation of the architecture components but the user-friendly features.