Updating a ruleset without updating tflint causes trouble #1522
-
IntroductionGenerally speaking it would be great if there would be a better update path. With tflint 0.40.0 and tflint-ruleset-aws 0.17.0 there is no way of updating one first and then the other. So if used in different repositories, both of them have to be updated at the same for all the repositories. I had a quite specific problem though, without having updated tflint I tried to run
Fair enough, so I updated my tflint, ran
But
I found the following:
Removed the 0.17.0 folder and ran
So apparently the ruleset got installed incorrectly in some way, Additional Context$ tflint -v
TFLint version 0.40.1
$ terraform --version
Terraform v1.3.0
on darwin_arm64 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Sure, but this isn't actionable at the moment. Any plugin-based system has to contend with this tradeoff of compatibility versus evolution. Terraform did this most notably from 0.11 to 0.12 with its provider plugin protocol. HashiCorp has paying customers and a full team dedicated to Terraform core, which allows them to invest much more effort up front and in long term planning. As a volunteer project, TFLint makes different tradeoffs and regularly breaks compatibility (thus 0.x) in order to allow the project to continue to rapidly evolve.
We'd need a fully reproducible example to discuss further and open an issue. Tried this quickly in a container and failed to reproduce the reported behavior. Started on [email protected] and [email protected]. Ran init. Installed $ tflint --version
TFLint version 0.40.1
+ ruleset.terraform (0.1.1-bundled)
+ ruleset.aws (0.17.0) |
Beta Was this translation helpful? Give feedback.
Sure, but this isn't actionable at the moment. Any plugin-based system has to contend with this tradeoff of compatibility versus evolution. Terraform did this most notably from 0.11 to 0.12 with its provider plugin protocol. HashiCorp has paying customers and a full team dedicated to Terraform core, which allows them to invest much more effort up front and in long term planning. As a volunteer project, TFLint makes different tradeoffs and regularly breaks compatibility (thus 0.x) in order to allow the project to continue to rapidly evolve.
We'd need a fully reproducible ex…