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

I would guess it would, but that would force me to run that every deployment, probably not ideal?

Some folks do refresh before every update (there’s an option for this in the CLI). When something changes in the cloud, the state needs to sync up. Or do you have ideas how we could handle this better?

Hmm, ok. No, I don't really have a better suggestion. The issue with slot swapping is that the infrastructure does change outside pulumi. But, i'm now attempting to work around it by adding a random connection string to the slot every time, which would force pulumi to update them.

I'm not sure if this helps, but having worked in aws for a long time and dealing with Stack Drift, I've found that trying to find ways to move the infrastructure that is changing out of the stack is helpful. For example, storing configurations in <https://stackoverflow.com/questions/59923820/azure-table-storage-for-housing-application-configuration|tablestorage >or <https://docs.microsoft.com/en-us/azure/azure-app-configuration/overview|azure app configuration> rather than an appconfig if they are going to change.

That said, this input is from an architectural standpoint and not going to solve your issue in pulumi. :smile: