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'm seeing an issue with deploying changes to an already running App Service, and the application files being completed wiped post deploy. Just experienced it, where the Pulumi changes were simply adding some diagnostic settings to the app service and adding some app settings for a Application Insights instance. I would expect to see the ap p service restart due to the app setting changes, but not a wipe of the application code completely.. Has anyone else experienced anything similar?

For anyone else that comes across this issue - I resolved it by adding the `WEBSITE_RUN_FROM_PACKAGE` app setting to the app service with a value of `1` in Pulumi. When deploying code through VS/Rider/deployment task in ADO/GH, this setting is automatically added to ensure the application is ran from the packaged version that exists on the app service file system.

As this wasn't defined in Pulumi, it was being wiped, along with the application files, leaving an empty app service.