Hi there, I dont know what suddenly happended but whatever I do I keep getting this error, even after stashing my changes, any ideas?

pulumi:pulumi:Stack (Connected-dev):
    error: Running program 'C:\dev\Connected\infrastructure/' failed with an unhandled exception:
    <ref *1> Error: Invalid asset encountered when unmarshaling resource property
        at deserializeProperty (C:\dev\Connected\infrastructure\node_modules\@pulumi\runtime\rpc.ts:578:27)
        at deserializeProperty (C:\dev\Connected\infrastructure\node_modules\@pulumi\runtime\rpc.ts:671:23)
        at deserializeProperty (C:\dev\Connected\infrastructure\node_modules\@pulumi\runtime\rpc.ts:605:28)
        at Object.deserializeProperties (C:\dev\Connected\infrastructure\node_modules\@pulumi\runtime\rpc.ts:181:24)
        at C:\dev\Connected\infrastructure\node_modules\@pulumi\runtime\resource.ts:798:33
        at Generator.next (<anonymous>)
        at C:\dev\Connected\infrastructure\node_modules\@pulumi\pulumi\runtime\resource.js:21:71
        at new Promise (<anonymous>)
        at __awaiter (C:\dev\Connected\infrastructure\node_modules\@pulumi\pulumi\runtime\resource.js:17:12)
        at resolveOutputs (C:\dev\Connected\infrastructure\node_modules\@pulumi\pulumi\runtime\resource.js:676:12) {
      promise: Promise { <rejected> [Circular *1] }
    }

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.

I guess you are after

azure-native

?

That works, thanks