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 |
||
---|---|---|
.. | ||
archive | ||
asset | ||
config | ||
plugin | ||
sig | ||
testing | ||
urn | ||
alias.go | ||
asset.go | ||
asset_test.go | ||
custom_timeouts.go | ||
errors.go | ||
mapper_test.go | ||
properties.go | ||
properties_diff.go | ||
properties_diff_test.go | ||
properties_path.go | ||
properties_path_test.go | ||
properties_test.go | ||
property_compatibility.go | ||
property_compatibility_test.go | ||
resource_goal.go | ||
resource_id.go | ||
resource_id_test.go | ||
resource_operation.go | ||
resource_state.go | ||
stack.go | ||
status.go | ||
urn.go |