pulumi/sdk/proto/go
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.pb.go Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
engine.pb.go Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
language.pb.go Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
plugin.pb.go Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
provider.pb.go Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00
resource.pb.go Save resource dependency information in the checkpoint file 2018-02-21 17:49:09 -08:00