From 648acf7331acc964153ff356b91d1457d13892b5 Mon Sep 17 00:00:00 2001 From: Geoffrey Wiseman Date: Sat, 26 Aug 2017 10:29:17 -0300 Subject: [PATCH] Describing Module Encapsulation Terraform modules encapsulate their resources, and dependencies can only be expressed through outputs, which wasn't clear to me in the existing documentation. I'm hoping a small change will make that more explicit. --- website/docs/modules/usage.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/modules/usage.html.markdown b/website/docs/modules/usage.html.markdown index 6a098b442..79782a746 100644 --- a/website/docs/modules/usage.html.markdown +++ b/website/docs/modules/usage.html.markdown @@ -84,7 +84,7 @@ Additionally, because these map directly to variables, module configuration can ## Outputs -Modules can also specify their own [outputs](/docs/configuration/outputs.html). These outputs can be referenced in other places in your configuration, for example: +Modules encapsulate their resources. A resource in one module cannot directly depend on resources or attributes in other modules, unless those are exported through [outputs](/docs/configuration/outputs.html). These outputs can be referenced in other places in your configuration, for example: ```hcl resource "aws_instance" "client" {