Enforce naming convention in the modules

[marianoc84]

I have this file tree:

.
├── locals.tf
├── main.tf
├── modules
│   └── vpc
│       ├── locals.tf
│       ├── main.tf
│       └── variables.tf
├── outputs.tf
├── providers.tf
├── .tflint.hcl
└── variables.tf

I have written a .tflint.hcl as the following:

plugin "terraform" {
    enabled = true
    preset  = "all"
}

plugin "aws" {
    enabled = true
    version = "0.32.0"
    source  = "github.com/terraform-linters/tflint-ruleset-aws"
}

rule "terraform_naming_convention" {
    enabled = true
}

and this is in the root folder of my terraform. If I run tflint --recursive and in modules/vpc/main.tf there's a wrong naming convention for a resource (e.g. myNewResource) nothing happen; but, if I copy the same .tflint.hcl file in the vpc directory the notice is shown correctly.

How can I enforce the naming convention in the module avoiding polutting the code with tons of .tflint.hcl files?

[bendrucker]

Use an absolute path if you don't want TFLint to try to load configuration relative to each directory:

https://github.com/terraform-linters/tflint/blob/master/docs/user-guide/config.md#configuring-tflint

By default, .tflint.hcl is loaded relative to the module under test. But if you pass an absolute path to the file at your repo root, it'll always load the same config.