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 error is brutal: `Invalid asset encountered when unmarshaling resource property`

`pulumi stack export` has the following data:
```{
    "urn": "[…]$command:local:Command::build-command",
    "custom": true,
    "id": "build-command5ffdbbd8",
    "type": "command:local:Command",
    "inputs": {
        "addPreviousOutputInEnv": true,
        "assetPaths": [
            "build/**"
        ],
        "create": "pnpm build --sourcemapClient --minify=false",
        "dir": "../../web-app"
    },
    "outputs": {
        "addPreviousOutputInEnv": true,
        "assetPaths": [
            "build/**"
        ],
        "assets": {
            "build/client/.DS_Store": {
                "4dabf18193072939515e22adb298388d": "c44067f5952c0a294b673a41bacd8c17",
                "hash": "9d19c5664746dacd091a0b016973eb023b8bdea8716e2b223b9153e8699e4c29"
            },
            […]
        },
        […]
    },
    […]
}```

the error comes from this line in `@pulumi/pulumi` :
<https://github.com/pulumi/pulumi/blob/e15e594b4e1b81edb36c03aac1d9f99aeee6bad8/sdk/nodejs/runtime/rpc.ts#L743>

as you can see, the `.DS_Store` asset has a `hash` property rather than the expected path/text/uri properties. this is the case for every asset in that `outputs.assets` map.

i suppose the workaround is to not use `assetPaths` on my `Command` resource

Are you on a recent version of Pulumi? I thought we'd fixed this issue, seen it before with azure-native refreshes

damn, can you raise an issue with details on where you saw this. We'll take a look.

i'd love to, but chasing a deadline and worked around this by avoiding `assetPaths` with `local.Command` (from `@pulumi/command`). some notes:
• assetPaths was an array containing a single relative glob
• the `stack export` output showed the `outputs.assets` of the command containing `{ hash }` objects
• the error shows up when running `update` after a `refresh` command
• error triggered by this line: <https://github.com/pulumi/pulumi/blob/e15e594b4e1b81edb36c03aac1d9f99aeee6bad8/sdk/nodejs/runtime/rpc.ts#L743>
i'm somewhat confident that's all you need to reproduce...

Copied bits of this thread to <https://github.com/pulumi/pulumi/issues/18926>