3 ms·
I'd say the argument is flawed. If you move to Pulumi, eventually you will have all the same problems you have with Terraform, except now it's written in a comp
by yuppie_scum 3y ago
I'd say the argument is flawed. If you move to Pulumi, eventually you will have all the same problems you have with Terraform, except now it's written in a complex language instead of HCL, which is easy to read, well documented and well suited to the infrastructure problem set. HCL and Terraform are also well supported in VSCode these days.
I would also say that the "set and forget" nature of terraform and versioning is fine, since it tends to just work at old versions and is usually forward compatible (since about the .14->1.0 split).
Now I am a hopeless TF stan but I am a bit concerned about the license change as well. Not so much for the FOSS crusader angle, but that the backlash may destroy a great tool ecosystem for devops/platform/SRE teams.
- jaxxstorm 3y agothis is absolutely not the experience we have when customers migrate to Pulumi, and I spend all day helping users undergo that transition.