This message was deleted.

I'd guess that there are in fact changes to be made but Pulumi doesn't let you know beforehand as it doesn't refresh the current state of the cloud resources before applying changes.

pulumi up/pre

operations don't refresh the state of the cloud APIs unless you pass in

pulumi up --refresh

(which is the default behavior in Terraform). See relevant discussion on GitHub. What I've started doing is explicitly setting this option in the project configuration

Pulumi.yaml

options:
  refresh: always

There's also an option that will fail if there are changes pending when you don't expect any. I find this particularly useful for detecting configuration drift. In combination with the

--diff

flag you can resolve any differences between state & actual cloud resources.

pulumi pre --expect-no-changes --refresh --diff