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

Globally, there is not, however, you can set it on a project level in the `Pulumi.yaml` file. <https://www.pulumi.com/docs/concepts/projects/project-file/#options-options>

`pulumi up` takes `--refresh` that will perform a refresh before an update. In fact, the `preview` and `destroy` commands also support that flag.

Thanks both of you.  it works.

Apparently it does two refreshes on `up`, one for the plan and one for the update.

Would love a way to avoid the refresh for the plan.  That’s a good compromise between speed and safety.  It’s no worse than the default of not refreshing … and it’s likely just as fast.  Presumably anything it msises will be handled the same as if a change happened while the user was reviewing the plan

Are you running this in CI? If so, you might be better off running `refresh` in its own step before you run an `up`. Might be slightly faster that way.

Ah ok. Not a whole lot of options then and running it implicitly is probably better so you are not having to run multiple commands during your dev loop.