This message was deleted.

Hum, ok I found out my problem. Actually the provider was

undefined

because of an error I did, but there was no clue at all about it. Maybe you should ensure when someone sets a

provider(s)

value in the

opts

of a component it is defined in since there’s no point to provide an undefined value voluntarily here.

Yes - very good idea. The one slight concern here is that generally

x: undefined

is treated the same as leaving

x

out of the object in the first place. This helps with compositionally. We'd be violating that equivalence if we errored in this case. Probably still worth doing that though to make this easier to discover/debug.

Yeah I was thinking about that too. But I think this could become a common mistake and that’s a nasty one to find out since there’s no clear error (pulumi fallback to the

kubectl

config if there’s no provider).