Linting fails under tflint 0.12.0

Given a very simple Terraform config file (not the real GUIDs and such):

provider "azurerm" {
  version         = "=1.35.0"
  subscription_id = "1fb2265c-7cd1-4d4f-bc67-61d7799765e8"
  tenant_id       = "f6586130-34a9-4ba8-917d-f78e55f72733"
}

resource "azurerm_resource_group" "kubernetes" {
  name     = "myrg"
  location = "West US"
}

Running linting (manually, since it doesn’t seem to auto-run?) yields the following error in the output window:

2019-10-08 18:38:54:080 [INFO ] <cmd>lint: undefined issues
2019-10-08 18:38:54:081 [ERROR] <cmd>lint: Linting failed for c:\Users\tillig\Desktop\Terraform TypeError: issues.forEach is not a function

I believe this will be fixed by PR #227

However, if I add something to my config file that would be found by linting, like an unpinned module…

provider "azurerm" {
  version         = "=1.35.0"
  subscription_id = "be62f057-87be-48e5-9c5f-c6fc74ac9d19"
  tenant_id       = "a172c77d-91cf-47f0-a813-30aee710c0dc"
}

resource "azurerm_resource_group" "kubernetes" {
  name     = "tillig-k8s"
  location = "West US"
}

module "unpinned" {
  source = "git://hashicorp.com/consul.git"
}

Running linting yields an error:

2019-10-08 18:44:26:069 [ERROR] <cmd>lint: Linting failed for c:\Users\tillig\Desktop\Terraform Error: Command failed: tflint --format json

I am guessing that when the current tflint finds errors it doesn’t exit with 0, it instead appears to exit with 3, so when linting sees any error, it doesn’t even try to parse the results.

It appears you can run tflint /force to require it to always exit 0 even if issues are found. Should that be added to the command line parameters?

[tillig]

@jeffb4 Are you able to do this update or should I fork and submit a new version of the PR? I’d love to see tflint working.

[aaronsteers]

I’m experiencing this as well with terraform 0.12 - is there nothing which can be done as a workaround to get tflint working in VS Code?