Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm not of a dissenting opinion on most of these experience reports, but

> TF binary versions need to be globally consistent,

honestly, shouldn't that kind of be your baseline goal for all tools that are on multiple hosts and taking part of your CI or development processes?



Yeah, sorry if I wasn't clear. I meant that the CI build servers do have a consistent version installed. But it is pretty hard to control what devs install on their laptops, and it is a little hard to write TF code without running `terraform plan` to test it, so a lot of devs may end up with TF installed. If they run `terraform apply` (and have access to write state) it could mess up the state file version.

Of course that is solved by using `terraform { required_version = "= x.x.x" }`, but that plays into my point about having tons of state files, not being able to use variables, editing tons of files, and updating tons of states.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: