https://pulumi.com
Join Slack
This message was deleted.
# getting-started
s
This message was deleted.
e
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 => i.id.apply(id=>parseInt(id)))
t
Thanks Fraser, but unfortunately that gives the same error about 
interface {} is string, not int
...
e
linodes:  [instances[0].id, instances[1].id]
works? The equivilant map for that is just: 
linodes: instances.map(i => i.id)
t
Yes, that's what I thought as well, but same error :(
e
that's very strange 😐 I'd raise an issue at https://github.com/pulumi/pulumi-linode about this, especially given that's a panic in the provider itself.
t
Ok Fraser, I'll do that, thanks for looking into this with me!
e
No worries, sorry the obvious thing didn't just work.
t
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?
e
probably, suggests that the typescript code is correct and it really is a provider bug in the Update method.
👍 1
Is it crashing at preview or update time?
t
preview
e
Maybe a bit risky but could you run an update with 
--skip-preview
and see if that works?
t
Nice, that works indeed 🙂
e
Ha, then yes definitely a provider bug. It's not handling unknown values at preview time correctly.
t
Indeed! Thanks for narrowing it down, that should make the issue easier to solve!
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by