The wording for refresh doesn't accurately convey that the operations aren't actually mutating your resources, but instead are simply changing your checkpoint state. This change (hopefully) helps in two ways: First, put text just before the prompt: Do you want to perform this refresh? No resources will be modified as part of this refresh; just your stack's state will be. Second, alter the summary ever-so-slightly, from: info: 2 changes performed: ~ 2 resources updated 3 resources unchanged to: info: 2 changes refreshed: ~ 2 resources updated 3 resources unchanged This reads just slightly better, and removes any sense of panic I might have otherwise had that my refresh just did something wrong. As I was in here, since I had to pass UpdateKind information to new places, I cleaned up the situation where we had three mostly-similar enums (but which actually diverged) and several areas where we were using untyped strings for this same information. Now there's just one. This fixes pulumi/pulumi#1551. |
||
---|---|---|
.. | ||
migrate | ||
cli.go | ||
core.go | ||
errors.go | ||
history.go | ||
logs.go | ||
stacks.go | ||
updates.go |