You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)?
Affected Resource(s)
Community Note
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.
The text was updated successfully, but these errors were encountered: