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

huh, this doesn't sound ideal. Woukd you be able to open an issue for this in <http://github.com/pulumi/pulumi-azure-native|github.com/pulumi/pulumi-azure-natve> with a repro?

I think I figured out part of it... it turns out the functions were still there, but the WEBSITE_ENABLE_SYNC_UPDATE_SITE and WEBSITE_RUN_FROM_PACKAGE settings were getting removed. The functions stick around if I add those settings to the pulumi stack, but other app settings I need still disappear.

This, I guess, is the real issue. I suppose makes sense because Pulumi believes it owns SiteConfig.AppSettings. However, is there any way to change this behaviour, i.e. stop it deleting settings pushed from elsewhere?