pulumi/pkg/resource/plugin
joeduffy ae92e68902 Return state as part of Create and Update¬
As part of the bridge bringup, I've discoverd that the property state
returned from Creates does *not* always equal the state that is then
read from calls to Get.  (I suspect this is a bug and that they should
be equivalent, but I doubt it's fruitfal to try and track down all
occurrences of this; I bet it's widespread).  To cope with this, we will
return state from Create and Update, instead of issuing a call to Get.
This was a design we considered to start with and frankly didn't have
a super strong reason to do it the current way, other than that it seemed
elegant to place all of the Get logic in one place.

Note that providers may choose to return nil, in which case we will read
state from the provider in the usual Get style.
2017-07-21 14:00:29 -07:00
..
analyzer.go Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
analyzer_plugin.go Make assets and archives 1st class 2017-07-14 12:28:43 -07:00
check.go Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
context.go Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
host.go Add some ReadLocations tracing; and skip nulls 2017-07-06 00:02:33 -04:00
host_server.go Make assets and archives 1st class 2017-07-14 12:28:43 -07:00
plugin.go Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
provider.go Return state as part of Create and Update¬ 2017-07-21 14:00:29 -07:00
provider_plugin.go Return state as part of Create and Update¬ 2017-07-21 14:00:29 -07:00
rpc.go Fix asset diffing 2017-07-17 10:38:57 -07:00
rpc_test.go Fix asset diffing 2017-07-17 10:38:57 -07:00