3 ms·
> But I certainly don‘t touch any IaC stuff that wouldn‘t allow me easily move between vendors. How does Terraform achieve that better than CF besides that it
by chrisandchris 5y ago
> But I certainly don‘t touch any IaC stuff that wouldn‘t allow me easily move between vendors.
How does Terraform achieve that better than CF besides that it has the ability to provision other providers? If you want to switch from say AWS to Azure, you are still required to reconfigure each and every resource as they are named differently, behave probably differently and have different parameters. In that time you probably have learned the equivalent of CF in Azure (if there is some).
It‘s not unachievable, but saying it‘s „easy“ is far away from the truth.
- Dobbs 5y agoBecause this can be done piecemeal and in place. Additionally if you use modules and the like it can be done in swaths without issue. Additionally you can tie things across domains. Use Route53 with Azure servers, etc.
- anothernewdude 5y agoHow does terraform make it easy to move between vendors when CF doesn't allow it at all? Is that actually a question you are seriously asking? The providers for AWS/Azure/Openstack/VSphere look very similar, to the extent that terragrunt templates can smooth over the differences. Calling renaming provider resources 'reconfiguring' is a stretch. If that's the worst thing you ever have to do, then I would suggest you're not doing much that is complicated in this space at all.