pulumi/sdk/proto/nodejs
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
..
analyzer_grpc_pb.js Add a manifest to checkpoint files (#630) 2017-12-01 13:50:32 -08:00
analyzer_pb.js Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
engine_grpc_pb.js Rename pulumi-fabric to pulumi 2017-09-21 19:18:21 -07:00
engine_pb.js Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
language_grpc_pb.js Consult the program for its list of plugins 2018-02-18 08:08:15 -08:00
language_pb.js Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
plugin_pb.js Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
provider_grpc_pb.js Add rudimentary delete-before-create support 2017-12-13 10:47:18 -08:00
provider_pb.js Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
resource_grpc_pb.js Simplify RPC changes 2017-11-29 12:08:01 -08:00
resource_pb.js Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00