pulumi/cmd
joeduffy dd9e6b35f4 Introduce an OpSame planning step
This change introduces an OpSame planning step.  The reason we need
this is so that we can apply the necessary output properties, including
the ID, even as we are simply walking the plan (i.e., when we aren't
actually performing a deployment).  This ensures that the object state
evolves as required to let reads of output properties propagate in the
ways necessary to reproduce past executions of the program.
2017-06-13 07:10:13 -07:00
..
lumi Introduce an OpSame planning step 2017-06-13 07:10:13 -07:00
lumidl Print output properties in the CLI 2017-06-01 08:37:56 -07:00
lumijs Add support for template literals in LumiJS 2017-06-09 18:46:09 -07:00
lumipy Finish scrubbing TODOs 2017-06-06 06:05:35 -07:00