Gergely Kalmár

I essentially mean that there should be an option where ctermfg and ctermbg is not set for the main (default/unhighlighted) text, this used to be the case, but isn't anymore...

Fair, I mean, it's more of a patch, but I guess it might work fine, thank you for the tip. FWIW I think this was the default behavior of vim...

The hooks as described in the documentation (https://terragrunt.gruntwork.io/docs/features/hooks/#tflint-hook) are not working anymore, I think this is a rather serious regression. The workarounds are quite involved with having to install tflint...

> [@GergelyKalmar](https://github.com/GergelyKalmar) I understand your frustration as I was in the same situation. However, I do believe this is the way forward as tools evolve and we can't stay on...

Not stale, I think this problem still exists.

@brikis98 I think the issue still persists. Reproducer: `terragrunt.hcl`: ``` remote_state { backend = "s3" config = true ? { bucket = "terraform-state-test" key = "test" region = "us-east-1" encrypt...

It works fine as long as the config map contains the same type of objects.

Any chance to expedite this issue? It seems there's many who would be eager to move over to trusted publishing now that it is the recommended approach, but not being...

That workflow is in the same repository though, I think the issue is with reusable workflows that are in a _different_ repository (e.g. in a separate public repo).

You can get around the `inherit` issue between organizations via forking, which is what we would usually do. So same org, different repo would be fine. The point of reusable...