I think you'll need some customization. The ability to create a database service in GCP vs AWS is a different syntax, but you still have the ability to re-use components. There is likely going to be things you need to do in both GCP and AWS that are similar... and can be reused, others will need to be specialized for each cloud Infra.
What I really like about terraform and what i want to use it for is to spin up/tear down entire environments and have everything live in source control.
Just my 2 cents. I'm going to be more heavily using terraform soon, but from all i've seen it's a pretty awesome tool.
I think you'll need some customization. The ability to create a database service in GCP vs AWS is a different syntax, but you still have the ability to re-use components. There is likely going to be things you need to do in both GCP and AWS that are similar... and can be reused, others will need to be specialized for each cloud Infra.
What I really like about terraform and what i want to use it for is to spin up/tear down entire environments and have everything live in source control.
Just my 2 cents. I'm going to be more heavily using terraform soon, but from all i've seen it's a pretty awesome tool.
The native tools also allow spin up and tear down of environments and infrastructure as code in any shape or form can be in source control.
I have a repo that contains all of my cloud formation and it is written in such a way that it is also reusable.
I guess what I was getting at is that the reusable code can be applied to multiple cloud environments which would be the appeal.
Though at the end of the day use whichever tool you like as long as it works for you.