pulumi/pkg
joeduffy 5fb014e53c Explicitly track default properties
This changes the RPC interfaces between Lumi and provider ever so
slightly, so that we can track default properties explicitly.  This
is required to perform accurate diffing between inputs provided by
the developer, inputs provided by the system, and outputs.  This is
particularly important for default values that may be indeterminite,
such as those we use in the bridge to auto-generate unique IDs.
Otherwise, we fail to reapply defaults correctly, and trick the
provider into thinking that properties changed when they did not.

This is a small step towards pulumi/lumi#306, in which we will defer
even more responsibility for diffing semantics to the providers.
2017-07-31 18:26:15 -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 Support for string.split 2017-07-21 14:00:30 -07:00
graph Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
integrationtesting Build/test the minimal Lumi program as a nightly integration test 2017-07-23 12:12:43 -06:00
pack Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
resource Explicitly track default properties 2017-07-31 18:26:15 -07:00
tokens Addres PR feedback on #288 2017-07-13 23:03:28 -07:00
tools Explicitly track default properties 2017-07-31 18:26:15 -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