From ddd0d2a4423be60764b1fa2b795853efbff62c56 Mon Sep 17 00:00:00 2001 From: Thomas Alton <47434488+talton-heb@users.noreply.github.com> Date: Wed, 12 Jun 2019 12:21:29 -0500 Subject: [PATCH] website: Provider proxy config only supports alias --- website/docs/configuration/modules.html.md | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/website/docs/configuration/modules.html.md b/website/docs/configuration/modules.html.md index 9d81357e3..969e17573 100644 --- a/website/docs/configuration/modules.html.md +++ b/website/docs/configuration/modules.html.md @@ -328,19 +328,17 @@ provider "aws" { Each resource should then have its own `provider` attribute set to either `"aws.src"` or `"aws.dst"` to choose which of the two provider instances to use. -At this time it is required to write an explicit proxy configuration block -even for default (un-aliased) provider configurations when they will be passed -via an explicit `providers` block: +A proxy configuration block is one that is either completely empty or that +contains only the `alias` argument. It serves as a placeholder for +provider configurations passed between modules. Although an empty proxy +configuration block is valid, it is not necessary: proxy configuration blocks +are needed only to establish which _alias_ provider configurations a child +module is expecting. -```hcl -provider "aws" { -} -``` - -If such a block is not present, the child module will behave as if it has no -configurations of this type at all, which may cause input prompts to supply -any required provider configuration arguments. This limitation will be -addressed in a future version of Terraform. +A proxy configuration block must not include the `version` argument. To specify +version constraints for a particular child module without creating a local +module configuration, use the [`required_providers`](/docs/configuration/terraform.html#specifying-required-provider-versions) +setting inside a `terraform` block. ## Multiple Instances of a Module