a626dcf6a3
This changes a few things in the CLI, mostly just prettying it up: * Label all steps more clearly with the kind of step. Also unify the way we present this during planning and deployment. * Summarize the changes that *did not* get made just as clearly as those that did. In other words, stuff like this: info: 2 resources changed: +1 resource created -1 resource deleted 5 resources unchanged and info: no resources required 5 resources unchanged * Always print output properties when they are pertinent. This includes creates, replacements, and updates. * Show replacement creates and deletes very distinctly. The create parts show up minty green and the delete parts show up rosey red. These are the "physical" steps, compared to the "logical" step of replacement (which remains marigold). I still don't love where we are here. The asymmetry between planning and deployment bugs me, and could be surprising. ("Hey, my deploy doesn't look like my plan!") I don't know what developers will want to see here and I feel like in general we are spewing far too much into the CLI to make it even useful for anything but diagnosing failures afterwards. I propose that we should do a deep dive on this during the CLI epic, pulumi/pulumi-service#2. This resolves pulumi/pulumi-fabric#305. |
||
---|---|---|
.. | ||
plan.go | ||
plan_apply.go | ||
plan_test.go | ||
progress.go | ||
snapshot.go | ||
source.go | ||
source_eval.go | ||
source_fixed.go | ||
source_null.go | ||
step.go | ||
target.go |