3 ms·
If terraform gets the job done and seems easier, then that is a good reason to use it. Especially as it seems that there are more boilerplate examples for terra
by jjeaff 8y ago
If terraform gets the job done and seems easier, then that is a good reason to use it. Especially as it seems that there are more boilerplate examples for terraform out there.
But no lock-in is not a reason at all. There is effectively no amount of terraform config that will plug and play into a different cloud.
It seems that it was pitched that way. But if you write anything in terraform for AWS you will have to fully rewrite it for GCP or DO. But at least you will be used to the syntax and conventions.
- meowface 8y agoThanks, that makes sense. I think a consistent syntax and data structures is definitely a still big benefit, even if it's not actually semantically vendor-agnostic. I think I'll probably keep using Terraform.
- scarface74 8y agoThat’s the problem. Of course AWS will have more boilerplate examples with CF. CodeStar is a whole library of CF based deployments. When you export a definition from a lambda you get CF. If you ever work for a company that uses AWS, they probably have a business support plan where you can get instant and excellent customer support on CF.
- Aeolun 8y agoOf course, if you use Terraform you likely wouldn’t need any support in the first place. Knowing Terraform is going to be a bit more helpful if you ever work with something other than AWS too.
- scarface74 8y agoRight because no one ever had issues with something as complicated as infrastructure set up. All the provisioners are different. If you have to learn new cloud infrastructure. Learning the IAC configuration is the least of your troubles.