Ben Drucker

Interesting. The provided directory gets two passes: Terraform loads the configuration, and tflint separately scans for annotations. The raw HCL bodies are also re-parsed from the source cache so rules...

TFLint plugins are sourced from GitHub releases. So this is definitely possible by paginating through releases until a match is found if a range is provided, rather than getting a...

Support for latest will come at the same time as ranges I think. We don't want to be steering the bulk of users towards `latest` while TFLint is still very...

> Dependabot does not support tflint, so this will lead to a lot of manual version bumping. Renovate might: https://docs.renovatebot.com/modules/datasource/ We might be able to write a Renovate preset that...

This seems like the most promising direction for automated version updates: https://docs.renovatebot.com/getting-started/use-cases/#custom-dependency-extraction Renovate can use GitHub tags/releases as a data source. It can be told how to parse the config...

To the original question, here's my updated thoughts: * Semver constraints require a lot of work, doubly so w/ GitHub as the backing API, and we're unlikely to ship that...

Using the latest version is inherently unpredictable, but Terraform allows it anyway. It's not necessarily a good idea but at most the software will print a warning. If you are...

Ok so I don't mind working on this a bit. As described above this would work like Terraform, minus constraints. - `version` is optional - When omitted, any installed version...

Why would we do this when suitable architecture-specific builds are already available? I see you've gone around posting form issues to a bunch of repos, but you have't explained why...

Was assuming universal builds were a separate build or otherwise delegated to Go but that's actually not the case. Go has no knowledge of multi-architecture builds—it generates separate arch-specific builds...