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've got another question, is there a rule of thumb on on when to use `foo.bar..ApplyT()` to enforce Pulumi to wait for the creation of a particular resource?

As one can see from my last questions and in particular the debugging question last Tuesday, Im still struggling with the simple task of chaining two providers .. I always the the error message of cannot be assumed .. just because the first one isn't ready, when the second one is being created ..

Even tough I properly chain these two with pulumi.Provider(myProvider) ..

Which I think _should_ be enough to make Pulumi recognize, that one resource depends on another one ..

I am under the impression, that I miss something important, as my code starts to become a cascade of .ApplyT()'s

What are you trying to achieve? Providers don’t generally do much on their own, so depending on them is very uncommon.