This message was deleted.

There's an inherent dependency analysis that Pulumi does by default. The key to thinking about this is that your entire code will run before any resources are modified/created/destroyed. It's basically making a list of instructions to do on your resources. If you run a function that depends a previously configured resource, it knows to put that further down the list. That said, if there's a very specific order you need things to run it, you can use the Depends On function: https://www.pulumi.com/docs/concepts/options/dependson/ This can override the automatic inference, which can cause problems, so use with care.

I’ll have a look. Thé Major issue I can think off the async nature of this. Create repo Wait or pause so another process somewhere builds and pushes the image Continue. Of course I could create the repository by hand, but that kind of defeats the purpose of using pulumi

So this is what I'm running into myself right now... And what I'm doing is embracing the "microstacks". Again, you have to think about that the resources aren't created or modified until the whole script has been completed. Look into Stack Outputs to understand more on that. https://www.pulumi.com/learn/building-with-pulumi/stack-outputs/ https://www.pulumi.com/docs/concepts/inputs-outputs/

That makes sense, I made a core project and another that depends on it but taking it further is worth looking. Thanks for the feedback!