mirror of https://github.com/pulumi/pulumi.git
1515db22f1
As well as responding to `Configure` gRPC calls, a resource provider
binary can also accept configuration from the engine via the
`PULUMI_CONFIG` environment variable. Presently, the engine will only
send configuration namespaced to the provider in question, and will
strip namespaces when doing so. So, given an example host configuration
of:
```
config:
aws:region: eu-west-1
foo:bar: baz
```
an `aws` provider will be provided with
`PULUMI_CONFIG='{"region":"eu-west-1"}'`, whereas a `gcp` provider will
receive `PULUMI_CONFIG='{}'`, matching neither `aws:region` nor
`foo:bar`.
This is problematic for dynamic providers, since they are authored in
and typically considered part of the user's program, and not as a
separate entity. Consequently it is not unreasonable for a dynamic
provider author to expect to have access to the entirety of the Pulumi
configuration through e.g. `pulumi.Config`, just like any other code in
their program -- #17050 and #4512 are two examples.
This commit makes us live up to this expectation. Dynamic providers now
receive all configuration values, with the namespaces preserved so that
existing `pulumi.Config` code can work in a dynamic provider like it
works everywhere else.
Fixes #17050
|
||
|---|---|---|
| .. | ||
| 20230917--engine--the-engine-now-sends-resource-names-and-types-in-provider-requests-as-well-as-the-combined-urn.yaml | ||
| 20240731--cli-display--fix-deletes-not-being-show-in-refresh-when-using-json-output.yaml | ||
| 20240901--sdkgen-go--allow-output-versioned-invokes-to-resolve-and-maintain-secrets.yaml | ||
| 20240905--sdkgen-python--correctly-case-python-package-names-in-package-add-link-instructions.yaml | ||
| 20240906--cli--recover-from-zero-byte-credentials-json-files.yaml | ||
| 20240906--cli-display--hide-unnecessary-rows-in-non-interactive-mode.yaml | ||
| 20240909--cli--using-pulumi_backend_url-no-longer-updates-credentials-json.yaml | ||
| 20240909--cli-state--show-the-full-set-of-delete-commands-necessary-to-remove-resources-from-the-source-stack-if-writing-to-it-fails.yaml | ||
| 20240909--cli-state--try-to-revert-changes-to-destination-stack-if-we-are-unable-to-save-the-source-stack-in-state-move.yaml | ||
| 20240910--engine--fix-parameterized-providers-not-downloading-correctly-when-found-from-state.yaml | ||
| 20240910--engine--support-pulumi-config-in-dynamic-providers.yaml | ||