https://pulumi.com logo
#typescript
Title
# typescript
f

fancy-artist-45287

05/08/2023, 4:29 PM
Hi there, I dont know what suddenly happended but whatever I do I keep getting this error, even after stashing my changes, any ideas?
Copy code
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] }
    }
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... 🤷‍♂️🤦‍♂️
e

echoing-dinner-19531

05/09/2023, 11:43 AM
per chance have you ran a
pulumi refresh
recently? I think I've seen cases of providers breaking the state of assets on refresh
f

fancy-artist-45287

05/09/2023, 2:02 PM
yeah we run refresh before each deploy in ci cd which may screw up the state, removing it and adding it works...
e

echoing-dinner-19531

05/09/2023, 3:01 PM
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.
f

fancy-artist-45287

05/09/2023, 3:02 PM
I guess you are after
azure-native
?
thats the npm package we use
I saw somebody else having the "same" problem but with a different Asset
e

echoing-dinner-19531

05/09/2023, 3:31 PM
That works, thanks
i

important-beach-52274

06/19/2023, 4:36 PM
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.
28 Views