You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support a .tflint-version file similar to .terraform-version.
#2543
100+ repositories, each with .pre-commit-config.yaml configured to run TFLint (amongst other things), and a .tflint.hcl configured for the versions of TFLint, the versions and rules to check, etc
All working nice, both locally, and in the repository pipeline.
Issue
Upgrading TFLint without needing to have EVERY repo updated along with every developer manually upgrade / downgrade their version of TFLint, depending upon the repository they are in, and the state of the upgrades.
Possible solution
Replicate/clone the concept of tfenv into tflenv (I did wonder abouttflintenv, but it seems a bit long).
By having essentially a proxy for the tflint command, the proxy can extract the required version, from .tflint-version (or possibly from .tflint.hcl but I think consistency is nicer), and so we can roll out the upgrades across the repositories as we wish. A developer will automatically have the required version installed if it is not already present.
As the plugins are already cached (~/.tflint.d/plugins/github.com/terraform-linters/tflint-ruleset-aws for example), having different versions of the plugins in .tflint.hcl is already catered for.
So, a repository gets an updated version in .tflint-version and no one has to worry about which version of the command or the plugins and it all "just works" in a pattern already well established in many systems (.terraform-version, .rbenv, .pyenv, .php-version, etc.)
I'm happy to work with anyone on this, but I don't want it to be "my" tool. I want it to be part of TFLint so it is then something others can more easily add to and trust.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Sort of extending from #1111, but not completely.
Current setup
100+ repositories, each with
.pre-commit-config.yamlconfigured to run TFLint (amongst other things), and a.tflint.hclconfigured for the versions of TFLint, the versions and rules to check, etcAll working nice, both locally, and in the repository pipeline.
Issue
Upgrading TFLint without needing to have EVERY repo updated along with every developer manually upgrade / downgrade their version of TFLint, depending upon the repository they are in, and the state of the upgrades.
Possible solution
Replicate/clone the concept of
tfenvintotflenv(I did wonder abouttflintenv, but it seems a bit long).By having essentially a proxy for the
tflintcommand, the proxy can extract the required version, from.tflint-version(or possibly from.tflint.hclbut I think consistency is nicer), and so we can roll out the upgrades across the repositories as we wish. A developer will automatically have the required version installed if it is not already present.As the plugins are already cached (
~/.tflint.d/plugins/github.com/terraform-linters/tflint-ruleset-awsfor example), having different versions of the plugins in.tflint.hclis already catered for.So, a repository gets an updated version in
.tflint-versionand no one has to worry about which version of the command or the plugins and it all "just works" in a pattern already well established in many systems (.terraform-version,.rbenv,.pyenv,.php-version, etc.)I'm happy to work with anyone on this, but I don't want it to be "my" tool. I want it to be part of TFLint so it is then something others can more easily add to and trust.
All reactions