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

I don't think you need pulumi.all for the instances array, it's just a plain array. So probably something like:
`instances.map(i =&gt; i.id.apply(id=&gt;parseInt(id)))`

Thanks Fraser, but unfortunately that gives the same error about `interface {} is string, not int`...

`linodes:  [instances[0].id, instances[1].id]` works?
The equivilant map for that is just:
`linodes: instances.map(i =&gt; i.id)`

Yes, that's what I thought as well, but same error :(

that's very strange :neutral_face: I'd raise an issue at <https://github.com/pulumi/pulumi-linode> about this, especially given that's a panic in the provider itself.

Ok Fraser, I'll do that, thanks for looking into this with me!

No worries, sorry the obvious thing didn't just work.

Hmm just now I noticed that the `map` method does work when initially creating the resources from scratch, but not when updating it after increasing the number of nodes. Is that maybe a clue?

probably, suggests that the typescript code is correct and it really is a provider bug in the Update method.

Is it crashing at preview or update time?

Maybe a bit risky but could you run an update with `--skip-preview` and see if that works?

Nice, that works indeed :slightly_smiling_face:

Ha, then yes definitely a provider bug. It's not handling unknown values at preview time correctly.

Indeed! Thanks for narrowing it down, that should make the issue easier to solve!

<https://github.com/pulumi/pulumi-linode/issues/220>