pulumi/sdk/proto
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
..
go Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
nodejs Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
python Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
analyzer.proto Add a manifest to checkpoint files (#630) 2017-12-01 13:50:32 -08:00
engine.proto Add a manifest to checkpoint files (#630) 2017-12-01 13:50:32 -08:00
generate.sh Add Python generation to our Protobufs/gRPC interfaces 2017-12-21 09:24:48 -08:00
language.proto Consult the program for its list of plugins 2018-02-18 08:08:15 -08:00
plugin.proto Consult the program for its list of plugins 2018-02-18 08:08:15 -08:00
provider.proto Add rudimentary delete-before-create support 2017-12-13 10:47:18 -08:00
resource.proto Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00