WARNING (mounting): The reference "..." in resource ... is ambigious. It will not be mounted.

[tlm-daniele-ricci]

Question:

Hi all,

I'm getting a lot of warnings like following one:

WARNING (mounting): The reference "module.name" in resource module.... is ambigious. It will not be mounted.

I actually have two questions:

1. What does it means? Which are the conditions for which this warning is raised?
2. But moreover, as it is a warning I suspect there's something wrong in my code: what can I do to solve it?

Thank you

[nwsparks]

we have started running into this on terraform 1.2.4 after updating to terraform compliance 1.3.33

i tried it both with and without fast parsing installed.

some initial digging

❗ WARNING (mounting): The reference "module.redshift" in resource module.iam.aws_iam_policy.iqies_redshift_user_policy is ambigious. It will not be mounted.

attempt to view state on that object:

$ terraform state show module.iam.aws_iam_policy.iqies_redshift_user_policy
No instance found for the given address!

This command requires that the address references one specific instance.
To view the available instances, use "terraform state

turns out the object is actually at a different address and is a list object

$ terraform state list | grep iqies_redshift_user_policy
module.iam.aws_iam_policy.iqies_redshift_user_policy[0]

[nwsparks]

i was able to reproduce this on the latest https://github.com/terraform-compliance/cli/releases/tag/1.3.34 and provided a simple way to reproduce it here https://github.com/nwsparks/tf-compliance-ambig

the issue seems to be when a module references outputs from another module.

@eerkunt sorry to ping you directly but this issue is fairly old and hoping you see the new update I'm providing. i'd contribute further if i could, but hopefully this helps.

[eerkunt]

The reason why it gives that warning is due to the lack of information while mounting resources to each other within the plan file.

The plan format changed a lot of course, I think we can revisit this issue and maybe refactor it a bit.

Thanks a lot, @nwsparks, I am checking this.

[nwsparks]

@eerkunt is there a way to suppress the warnings in the meantime?