Terraform provides the same _workflow_ across clouds, not the same resource model (which would be dumb, since it would necessarily provide only a lowest common denominator representation).
> It is not possible to have a "resource vm { name = ... provider = aws }"
It actually is via modules. It’s a lot of work with basically no benefit though, so in practice people don’t do this.
Pulumi is better at specifically this kind of thing however, since you can implement a common interface which can be specialised for each available cloud.
Heck, I never get how terraform can be cloud-agnostic... If everybody thinks having a same language (HCL) is equalivent to cloud agnostic, YAML exists...
It is literrally impossible to create a simple VM in 2 different cloud providers without defining them twice with their own specific parameters.
If you use AWS provider, resources start with aws_, if it's GCP it starts with gcp_ and so on. It is not possible to have a "resource vm { name = ... provider = aws }"