5 ms·
I think I get the point of your comment but can you expand? For instance, I’ve resorted to pinning a specific terraform version and plug-in version in a custom
by networkchad 3y ago
I think I get the point of your comment but can you expand? For instance, I’ve resorted to pinning a specific terraform version and plug-in version in a custom docker container. I can use the same TF scripts I wrote 4 years ago against the AWS API which has not changed since.
- quickthrower2 3y agoYes I think your case is OK. The question is more say your team decides to use a new feature, let's say it is GPT5 via Azure for example, with TF. Then you need to keep up to date. I am not heavily into TF so I don't know if that is possible with the pinned terraform and using later providers versions or how that works. But it seems more hassle than just using the latest of everything. Note I am talking about "keeping up" as a general need for IaC - but it might turn out that the TF fork is a better place to do that in the long term. Time will tell.
- networkchad 3y agoGotcha. I misunderstood the keeping up context. I chased TF version updates for a while before being annoyed at having to retool significant parts of my long existing scripts. I gave up and just stuck to a version for what I needed. My only concerns is I may neglect a security update, but this is for personal stuff and not for anything that others use/consume.