pulumi/sdk/proto
joeduffy 9f160a7f91 Configure providers at well-defined points
As explained in pulumi/pulumi-fabric#293, we were a little ad-hoc in
how configuration was "applied" to resource providers.

In fact, config wasn't ever communicated directly to providers; instead,
the resource providers would simply ask the engine to read random heap
locations (via tokens). Now that we're on a plan where configuration gets
handed to the program at startup, and that's that, and where generally
speaking resource providers never communicate directly with the language
runtime, we need to take a different approach.

As such, the resource provider interface now offers a Configure RPC
method that the resource planning engine will invoke at the right
times with the right subset of configuration variables filtered to
just that provider's package.  This fixes pulumi/pulumi#293.
2017-09-04 11:35:21 -07:00
..
go Configure providers at well-defined points 2017-09-04 11:35:21 -07:00
nodejs Configure providers at well-defined points 2017-09-04 11:35:21 -07:00
analyzer.proto Alter the way unknown properties are serialized 2017-07-21 14:00:30 -07:00
engine.proto Wire up Lumi to the new runtime strategy 2017-09-04 11:35:21 -07:00
generate.sh Implement initial Lumi-as-a-library 2017-09-04 11:35:20 -07:00
languages.proto Wire up Lumi to the new runtime strategy 2017-09-04 11:35:21 -07:00
provider.proto Configure providers at well-defined points 2017-09-04 11:35:21 -07:00