Overall Satisfaction with HashiCorp Terraform
I use HashiCorp Terraform to create development and production assets in AWS, Digital Ocean, and Linode environments.
- It has a rich set of plugins to with with many cloud providers
- It tracks the state of your assets, if they exist or need to be built or changed
- It's easy to collaborate with others by sharing the state file
- In my opinion, simple tasks like rebooting a server are cumbersome
- Some cloud providers may not offer full support for all features of HashiCorp Terraform
- Tracking the state of cloud assets
- Automating the procurement of assets
- Ability to collaborate with others to do those things
- Once the assets are defined, it basically eliminates the overhead of expanding existing resources
- It reduces vendor-lock by making it easier to port resources from vendor to vendor
I'm beginning to look at Pulumi. In my opinion, it looks like it would be a good replacement for HashiCorp Terraform, and it has the advantage of configuration via scripting, rather than via HCL, which is HashiCorp Terraform configuration markup language. In my opinion, the Pulumi scripts look simpler to develop and maintain than the HCL equivalent.
Do you think HashiCorp Terraform delivers good value for the price?
Yes
Are you happy with HashiCorp Terraform's feature set?
Yes
Did HashiCorp Terraform live up to sales and marketing promises?
Yes
Did implementation of HashiCorp Terraform go as expected?
No
Would you buy HashiCorp Terraform again?
Yes