No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

nothing, if there were no external changes to the state of your resources

thanks Komal :slightly_smiling_face: I implemented by following this example where a refresh always occurs before an up: <https://github.com/pulumi/automation-api-examples/blob/main/nodejs/inlineProgram-tsnode/index.ts#L82-L84>

I had an issue where my `databricks:token` expired and I kept getting an error that I didn't understand, even though I was using the new token before the refresh in a `setConfig` call, the `refresh` was still failing (presumably because it was not using the new token)

The fix was to comment out the `refresh` call - so I wonder why it's used in the examples if it's not required?

Often folks want to refresh just in case there was drift on the cloud provider side (ie someone made manual changes within the AWS console).