pulumi/sdk/nodejs/runtime
Sean Gillespie ad06e9b0d8
Save resource dependency information in the checkpoint file
This commit does two things:
    1. All dependencies of a resource, both implicit and explicit, are
    communicated directly to the engine when registering a resource. The
    engine keeps track of these dependencies and ultimately serializes
    them out to the checkpoint file upon successful deployment.
    2. Once a successful deployment is done, the new `pulumi stack
    graph` command reads the checkpoint file and outputs the dependency
    information within in the DOT format.

Keeping track of dependency information within the checkpoint file is
desirable for a number of reasons, most notably delete-before-create,
where we want to delete resources before we have created their
replacement when performing an update.
2018-02-21 17:49:09 -08:00
..
native Support serializing methods to the inside layer. (#904) 2018-02-09 14:22:03 -08:00
closure.ts Ship nativeruntime.node as part of the SDK 2018-02-16 18:12:33 -08:00
config.ts Improve failure messages (#932) 2018-02-14 09:55:02 -08:00
debuggable.ts Treat unhandled promise rejections as uncaught exceptions. 2017-12-13 17:24:47 -08:00
index.ts Move language host logic from Node to Go (#901) 2018-02-10 02:15:04 +00:00
invoke.ts Introduce Output<T> and update Resource construction code to properly handle it. (#834) 2018-02-05 14:44:23 -08:00
resource.ts Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
rpc.ts Introduce Output<T> and update Resource construction code to properly handle it. (#834) 2018-02-05 14:44:23 -08:00
settings.ts Improve failure messages (#932) 2018-02-14 09:55:02 -08:00
stack.ts Introduce Output<T> and update Resource construction code to properly handle it. (#834) 2018-02-05 14:44:23 -08:00