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.

James Bardin d0cc7f1d5e resolve provider types when building the config ... All the information is available to resolve provider types when building the configuration, but some provider references still had no FQN. This caused validation to assume a default type, and incorrectly reject valid module calls with non-default namespaced providers. Resolve as much provider type information as possible when loading the config. Only use this internally for now, but this should be useful outside of the package to avoid re-resolving the providers later on. We can come back and find where this might be useful elsewhere, but for now keep the change as small as possible to avoid any changes in behavior.		5 years ago
..
empty	…
implied-providers	configs: Fix for resources with implied providers	6 years ago
nested-providers-fqns	resolve provider types when building the config	5 years ago
override-dynamic-block-base	…
override-dynamic-block-override	…
override-module	configs: include "providers" when overriding modules (#25496)	6 years ago
override-output-sensitive	…
override-resource-provider	…
override-variable	…
override-variable-sensitive	Remove sensitive_variables experiment	5 years ago
provider-aliases	old comment	5 years ago
provider-meta	validate provider_meta contains no interpolations	5 years ago
providers-fqns	…
required-providers-after-resource	…
required-providers-overrides	…