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

This was caused by a `FileAsset` I have no idea why. I commented out the specific code, ran `pulumi up`, put it inn again and another `pulumi up` and it worked again. Lets see how long it lasts this time... :man-shrugging::man-facepalming:

per chance have you ran a `pulumi refresh` recently? I think I've seen cases of providers breaking the state of assets on refresh

yeah we run refresh before each deploy in ci cd which may screw up the state, removing it and adding it works...

If you can open an issue against which ever resource provider that's using that FileAsset that would help. It's almost certainly a bug in the providers refresh method. But we need to know which provider to go look at to fix it.

<@U02J3T6A8LB> <https://github.com/pulumi/pulumi-azure-native/issues/642#issuecomment-1540334135> would this work?

I saw somebody else having the "same" problem but with a different Asset

For posterity, this does seem to be azure-native specific relating to the Blob resource after a `pulumi refresh.`

Workaround is to comment out the blob, `pulumi up`, then restore the blob.