pulumi/pkg
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
..
compiler Make assets and archives 1st class 2017-07-14 12:28:43 -07:00
diag Add a --debug option to plan, deploy, and destroy 2017-07-13 17:13:19 -07:00
encoding Support try/catch in Lumi and async/await in Node.js 2017-07-07 12:47:27 -07:00
eval Add a rudimentary toString runtime helper 2017-07-17 13:43:59 -07:00
graph Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
integrationtesting Fix golint errors in previous commit 2017-07-13 12:40:10 -07:00
pack Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
resource Return state as part of Create and Update¬ 2017-07-21 14:00:29 -07:00
tokens Addres PR feedback on #288 2017-07-13 23:03:28 -07:00
tools Return state as part of Create and Update¬ 2017-07-21 14:00:29 -07:00
util Add a --debug option to plan, deploy, and destroy 2017-07-13 17:13:19 -07:00
workspace Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00