Support aggregation for module_name in provider meta

[morgante]

Affected Resource(s)

• google_*

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Currently, the provider_meta block with module_name only picks up the nearest definition. This works fine for simple modules, but if a module includes submodules the submodule resources will only be attributed to the submodule.

Instead, we should aggregate the names of all parent modules for a resource so they can all be attributed.

[rileykarson]

Spoke with SDK folks- this is unlikely to happen anytime soon, and they're unsure if it's feasible. Would it be possible to plumb attribution through an input on the submodule(s)?

[morgante]

Thanks for checking Riley, looks like we can work around this with variables (ref. terraform-google-modules/terraform-google-kubernetes-engine#830).

[bharathkkb]

@rileykarson looks like provider_meta interpolation was not meant to be supported upstream hashicorp/terraform#28061. We reverted terraform-google-modules/terraform-google-kubernetes-engine#830 via terraform-google-modules/terraform-google-kubernetes-engine#845. We may have to explore other options to support this.

[rileykarson]

FYI @megan07