loud-nest-1572406/25/2018, 3:15 PM
colossal-beach-4752706/25/2018, 3:18 PM
, it does the comparison against what is stored on pulumi.com. (i.e. the last time
was ran against that stack, which may have been from a different user.) If changes to the infrastructure were made outside of Pulumi, it’s possible you can run into conflicts that would cause issues with the subsequent update. You can run
which will “sync” the current state of cloud resources with what is stored on Pulumi.com. i.e. bring in any updates made manually. However, there isn’t a way to just answer the question “has a change been made outside of Pulumi.”
loud-nest-1572406/25/2018, 3:22 PM
white-balloon-20506/25/2018, 3:25 PM
presents a preview prior to doing the refresh - so it will tell you what changes have been made in the target environment which are not represented in the current checkpoint. As Chris notes, you can accept those and update the checkpoint to match the target cloud environment. You would of course then need to decide what if any changes you want to make sense to the desired state represented in your Pulumi program, depending on whether you wanted to make those manual patches permanent, or wanted to intentionally overwrite them with another desired state.
loud-nest-1572406/25/2018, 3:31 PM
white-balloon-20506/25/2018, 3:47 PM
flag, and failing CI if that doesn't pass. See https://github.com/pulumi/pulumi/pull/1394.
loud-nest-1572406/25/2018, 4:11 PM