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

The `Blob` resource should get replaced, which causes `codeBlobUrl` to change, which causes the web app settings update, which should lead to the new code deployed after Azure figures it out.

Don't suppose you've done something similar with slot switching?

I haven’t done it with the native provider.

interesting... have you done this with a .NET 5.0 function yet?

No. But I expect no difference in deployment.

there's some notes about the fact that .NET 5 can only be deployed using the functions commandline right now

what's interesting here is that the blob url remains the same as the code for the example creates it with a static name, and doesn't appear to detect that the code in the publish folder has changed.

Managed to get .NET 5 working, relatively simple, just needs the runtime changing to `dotnet-isolated`

&gt;  what’s interesting here is that the blob url remains the same as the code for the example creates it with a static name
is there no autoname suffix? or does it not change between updates?

the autoname doesn't change, as it seems like it thinks the resource has been created.

oh, I think it might be a bug then. could you open an issue and I will check next week?

I think it's actually a little worse than that... even having the name include the datetime is causing problems with the azure function now.

hopefully shortly I'll have a fully replicatable example for you to clone.

hmm, it's at least not killing my function now...

<https://github.com/martinjt/pulumi-dotnet5>

That's the example, working "ish", but I'd prefer to have the function app's zip container not be deleted each time.