5 ms·
That's not at all how it works. Terraform supports each of those providers, but the resources are specific to each provider. You cannot use the same Terraform
by merlincorey 7y ago
That's not at all how it works.
Terraform supports each of those providers, but the resources are specific to each provider.
You cannot use the same Terraform configuration on AWS and Azure.
Nor would you want to, per se.
As far as I know, this is by design.
- EdwardDiego 7y agoFair criticism, I've never used it, just what I've picked up from their marketing material.
- techntoke 7y ago> Basically Terraform is cloud agnostic, so you can (theoretically) define something in Terraform and then use it on AWS, or GCP, or Azure. > Fair criticism, I've never used it, just what I've picked up from their marketing material. LOL, why'd you even comment? You are making statements based on marketing material? Microsoft is probably hiring people like you if you're looking for a job.
- tedk-42 7y agoBahahahaha spot on.
- dang 7y agoPersonal attacks will get you banned here, regardless of how ignorant or annoying some other comment is. Please review the guidelines and follow them when posting to HN: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- kitotik 7y agoYou can’t share provider-specific resources across providers of course, but you can absolutely share other configuration data across providers. I find it extremely useful - for example it’s fairly trivial to bounce between scaleway, AWS, DO, Vultr, etc.
- happythought 7y agoYou can also use the same basic cicd pipeline to manage infrastructure on different providers instead of a custom pipeline for each provider tailored to their tool.