Marco Ferrari

I think this is, in fact, an issue. To "detect" a Terragrunt file, we just check the extension: https://github.com/github/super-linter/blob/e277edca06d0850200869e6552a94da09f95cb3a/lib/functions/buildFileList.sh#L744 IIRC, `.hcl` may not be necessarily specific to Terragrunt (or Terraform)....

The lowest hanging fruit would be to exclude `docker-bake.hcl` as we did in https://github.com/github/super-linter/pull/1707, but maybe there's a more scalable approach?

The main Terragrunt configuration file is (by Terragrunt default) named: `terragrunt.hcl`. From the Terragrunt docs, it appears it might also support configuration using multiple HCL files, not just `terragrunt.hcl`, but...

This is a fair request, also considering that [YAML recommends using the yaml extension when possible](https://yaml.org/faq.html). I suppose this requires a bit more to generalize to other files as well....

Correct, we already pass the `-x` option (short form for `--external-sources`). @Kurt-von-Laven can you post the snippet that triggers the shellcheck issue?

https://github.com/koalaman/shellcheck/wiki/SC1091 suggests: ``` In case you have access to the file, e.g. if it is included in your source code repository: # shellcheck source=somefile source somefile ``` Did you try...

I think this is not super-linter's fault, but rather https://github.com/koalaman/shellcheck/issues/1250

you could play a bit with `envsubst` when running super-linter, but maybe that would make things a bit obscure.

Hi @Kurt-von-Laven . Having (or not) a `.shellcheckrc` in our templates doesn't matter. If you set `LINTER_RULES_PATH`, super-linter should pick yours up. To confirm, have a look at the output...

This is actually a feature request, more than a bug. #1900 (which introduced the `.shellcheckrc` template file) is not enough for that file to be picked up and passed to...