ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

website: Provider requirements are not inherited 

Add a note to the provider configuration section explaining that only
config can be inherited by child modules, not source or version
requirements.
This commit is contained in:
Alisdair McDiarmid 2020-08-25 13:02:16 -04:00
parent 7a34d4d709
commit 5f43934d5f
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/configuration/modules.html.md
View File

@ -372,6 +372,8 @@ resource "aws_s3_bucket" "example" {
We recommend using this approach when a single configuration for each provider We recommend using this approach when a single configuration for each provider
is sufficient for an entire configuration. is sufficient for an entire configuration.
~> **Note:** Only provider configurations are inherited by child modules, not provider source or version requirements. Each module must [declare its own provider requirements](provider-requirements.html). This is especially important for non-HashiCorp providers.
In more complex situations there may be In more complex situations there may be
[multiple provider configurations](/docs/configuration/providers.html#alias-multiple-provider-configurations), [multiple provider configurations](/docs/configuration/providers.html#alias-multiple-provider-configurations),
or a child module may need to use different provider settings than or a child module may need to use different provider settings than