This message was deleted.

I think so, the component won't register and resolve until it's dependencies resolve and the parent properties won't resolve till after that.

so I wrote a small pulumi program in csharp to test out the concept - from what I see, the answer is nope - no dependancies from the "parent" are waited on - resources require specific dependsOn attributes to be set in the component resource options instance.

ah yeh this might vary from language to language based on order of class constructors run, something we know we ought to make more consistent