Ben Drucker

That change conflicts a bit with existing config handling but a WIP that I tested against a real monorepo worked as expected: https://github.com/terraform-linters/tflint/tree/walk-up-config

That example would be a good fit for TFLint as it exists today. If you invoke TFLint on the root directory with `--module`, it will follow the module calls and...

This doesn't seem viable to me. TFLint uses Terraform as a library. Strictly speaking, it is only compatible with the version of Terraform it was built with, though many configurations...

Hmm, I guess as part of the release process we could find the Terraform version with `go list` and update a JSON file where the keys are TF versions and...

Whoa, impressive! I think it'd be fine to just do this going forward and perhaps manually backfill a TFLint version or two for 0.13 and 0.14. It'd be nice to...

Let's hold for now, really appreciate you sharing these scripts. I want to try to focus on the future of both TFLint and Terraform. It's also worth pointing out that...

> Can you add support to pull from the same places at terraform can for modules? Short answer is no, but it would be helpful to at least collect some...

At this stage, I don't think it's appropriate for TFLint to be taking on support for another release API. The plugin discovery system is very new and adding support for...

TFLint also exposes objects that are involved in configuration parsing, so you could conceivably write your own binary (replacing `tflint --init`) that could resolve/download plugins from sources other than GitHub.

> We use gitlab every day for our modules so I'm not sure why you keep saying it doesn't support it? The public Terraform registry that HashiCorp runs only supports...