You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Alisdair McDiarmid dcb8b45e0f configs: Fix for resources with implied providers ... Previously, resources without explicit provider configuration (i.e. a `provider =` attribute) would be assigned a default provider based upon the resource type. For example, a resource `foo_bar` would be assigned provider `hashicorp/foo`. This behaviour did not work well with community or partner providers, with sources configured in `terraform.required_providers` blocks. With the following configuration: terraform { required_providers { foo = { source = "acme/foo" } } } resource foo_bar "a" { } the resource would be configured with the `hashicorp/foo` provider. This commit fixes this implied provider behaviour. First we look for a provider with local name matching the resource type in the module's required providers map. If one is found, this provider is assigned to the resource. Otherwise, we still fall back to a default provider.		6 years ago
..
empty	…
implied-providers	configs: Fix for resources with implied providers	6 years ago
nested-providers-fqns	terraform: large refactor to use Provider from configs.Resource (#24396)	6 years ago
override-dynamic-block-base	…
override-dynamic-block-override	…
override-module	…
override-output-sensitive	…
override-resource-provider	configs: attach provider fqn to Resource (#24382)	6 years ago
override-variable	…
providers-fqns	…
required-providers-after-resource	configs: Simplify required_providers blocks	6 years ago
required-providers-overrides	configs: Simplify required_providers blocks	6 years ago