link configuration aliases between pages

This commit is contained in:
James Bardin 2021-02-12 14:49:00 -05:00
parent 1bb602859a
commit dfd8424392
2 changed files with 6 additions and 4 deletions

View File

@ -36,10 +36,10 @@ module "example" {
## Default Behavior: Inherit Default Providers
If the child module does not declare any configuration aliases, the `providers`
argument is optional. If you omit it, a child module inherits all of the
_default_ provider configurations from its parent module. (Default provider
configurations are ones that don't use the `alias` argument.)
If the child module does not declare any [configuration aliases](/docs/language/modules/develop/providers.html#provider-aliases-within-modules),
the `providers` argument is optional. If you omit it, a child module inherits
all of the _default_ provider configurations from its parent module. (Default
provider configurations are ones that don't use the `alias` argument.)
If you specify a `providers` argument, it cancels this default behavior, and the
child module will _only_ have access to the provider configurations you specify.

View File

@ -73,6 +73,8 @@ settings come from provider _configurations_, and a particular overall Terraform
configuration can potentially have
[several different configurations for the same provider](/docs/language/providers/configuration.html#alias-multiple-provider-configurations).
## Provider Aliases Within Modules
To declare multiple configuration names for a provider within a module, add the
`configuration_aliases` argument: