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

How do I get `pulumi refresh` to use the latest configuration values? I have a `databricks:token` that recently expired and I am trying update the stack, I've run the "recovering configuration" steps in a new folder and running `config get databricks:token` does show the correct token so I'm not sure why refresh is using the old config value

I've called the databricks API manually with the token to confirm it works.

I've also tried running with --verbose 10 but getting no extra output

There appears to be a token on the Databricks provider resource, I suspect this is where the old token is cached. How can I update it?

I’m unsure how to help with the Databricks issue, but to see the logs when setting verbose logging have you looked in or your OS temp directory? There should be a symlink named <http://pulumi.INFO|pulumi.INFO> pointing at the logs for the most recent run. That is unless you re adding `--logtostderr --logflow` flags to your command, see the <https://www.pulumi.com/docs/support/troubleshooting/#verbose-logging|docs> for more options