pulumi/pkg/resource/plugin
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
..
analyzer.go Make more progress on the new deployment model 2017-06-13 07:10:13 -07:00
analyzer_plugin.go Make more progress on the new deployment model 2017-06-13 07:10:13 -07:00
check.go More progress on pulumi/lumi#90 2017-06-13 07:10:13 -07:00
context.go Rewrite plans and deployments 2017-06-13 07:10:13 -07:00
host.go Rewrite plans and deployments 2017-06-13 07:10:13 -07:00
plugin.go Overhaul resources, planning, and environments 2017-06-13 07:10:13 -07:00
provider.go More progress on pulumi/lumi#90 2017-06-13 07:10:13 -07:00
provider_plugin.go Introduce an OpSame planning step 2017-06-13 07:10:13 -07:00
rpc.go Make more progress on the new deployment model 2017-06-13 07:10:13 -07:00