4 points | by sebkow 2 hours ago
6 comments
It's pretty much ubiquitous to me.
And, BTW, I usually joke Terraform had bugs before the first line of code was written. What's even the point of caching a state if the state can be changed behind Terraform's back.
Feels like a shill article for Pulumni.
I am not bashing Pulumni, or glorifying Terraform, but the examples shown in the article are simple, and do not proof any of the mentioned advantages.
I would even go further that an infrastructure definition language should NEVER be Turing-complete.
Seemed like trash when I used it
Terraform was always been trash. It lacked functionality it said it had on the tin. Hashicorp was good at marketing
It's pretty much ubiquitous to me.
And, BTW, I usually joke Terraform had bugs before the first line of code was written. What's even the point of caching a state if the state can be changed behind Terraform's back.
Feels like a shill article for Pulumni.
I am not bashing Pulumni, or glorifying Terraform, but the examples shown in the article are simple, and do not proof any of the mentioned advantages.
I would even go further that an infrastructure definition language should NEVER be Turing-complete.
Seemed like trash when I used it
Terraform was always been trash. It lacked functionality it said it had on the tin. Hashicorp was good at marketing