Yoriyasu Yano

> Also talking about pipeline agents and the fact that multiple teams actively work on all the modules, it seems very hard to follow the setup you described. This setup...

`.yml` is still supported and can be used, but with the introduction of `read_terragrunt_config`, you can also use `.hcl` for that purpose. The benefit of using `hcl` over `yaml` is...

The feature you are looking for is the `import` block which just completed the design cycle, but is not implemented yet. See the RFC for more details: https://github.com/gruntwork-io/terragrunt/blob/master/_docs/rfc/imports.md

You can read the parent as well, but you can't have cycles. That is, you can't have the child read the parent to expose child vars to the parent, while...

Unfortunately, that is not supported. `locals` are local to the configuration that defined it (that's why they are called "local", as opposed to "global") and are not automatically merged across...

Just to confirm, is this an issue with a pre-commit hook you are using, or are you manually running `terragrunt validate`?

Can you point to which `pre-commit` hook runs `terragrunt validate`? I don't see one in our list that runs `terragrunt validate` (only `terraform validate`). In any case, I think this...

Also, this is sort of expected behavior since `terragrunt validate` actually means to run `terraform validate` for the given terragrunt configuration, and the root terragrunt config doesn't point to a...

Ah yes SealedSecrets is probably the right way to go for this!

`kubergrunt` doesn't use the credentials from the aws profile (because it is an external binrary), and instead relies on the environment. AFAIK, this feature (sharing authentication between scripts and provider)...