4 ms·
I'm not sure I understand #1. Your points would still apply if a resource (e.g. aws_instance.foo) is created in one module and then referenced as a data source
by joombaga 5y ago
I'm not sure I understand #1.
Your points would still apply if a resource (e.g. aws_instance.foo) is created in one module and then referenced as a data source (e.g. data.aws_instance.foo) in another module. Are you suggesting remote state is different? Or would you also advise against referencing data source attributes from resources created in other modules?
- etxm 5y agoOh for sure, that’s point #4, but at least it’s in the same apply. In #1 there is also a tight coupling between two different sources. If team A changes their output, the dependent team B's references break. Also 1.2: security. If I can read an attribute from your state file, I can read the whole thing.