Skip to content

Commit 4b66133

Browse files
docs: clarify explicit providers don't inherit default provider config (#20888)
Fixes #20887 Co-authored-by: workprentice <257153108+workprentice@users.noreply.github.com>
1 parent e9b3dd7 commit 4b66133

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

content/docs/iac/concepts/providers/_index.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -463,6 +463,18 @@ resources:
463463
pulumi config set aws:region us-west-2
464464
```
465465

466+
{{% notes type="info" %}}
467+
Explicit providers don't automatically inherit configuration values set on the default
468+
provider of the same type. In the example above, if `aws:profile`, `aws:assumeRole`, or
469+
`aws:allowedAccountIds` were set in stack configuration for the default AWS provider, the
470+
`useast1` explicit provider would still need those same values passed to it directly; it
471+
starts from an empty configuration rather than copying the default provider's settings.
472+
If several explicit providers (or an explicit provider and the default provider) need to
473+
share credentials or account-level settings, read those values once from your stack
474+
configuration and pass them to each provider explicitly, rather than relying on any
475+
implicit inheritance.
476+
{{% /notes %}}
477+
466478
Component resources also accept a set of providers to use with their child resources. For example, the EC2 instance parented to `myResource` in the program below is created in `us-east-1`, and the Kubernetes pod parented to myResource is created in the cluster targeted by the `test-ci` context.
467479

468480
{{< chooser language "typescript,python,go,csharp,java,yaml" >}}

0 commit comments

Comments
 (0)