Hi there, I’m trying to understand how

dependsOn

works and if it’s the solution to my problem. From what I understand here https://www.pulumi.com/docs/intro/concepts/programming-model/#dependson it should properly wait for a previous resource to be available for the one I’m referencing it in. In my usecase I provision postgresql with an helm chart and my migration service needs to wait in order to connect to it. Unfortunately, having inputs from the chart nor having it explicitly define in the

dependsOn

does not make my service wait for all the services in the chart available and of course it fails since the database service is not available yet. How am I supposed to properly define dependencies when pulumi fails to understand a specific case then ?

did you add

dependsOn

to the chart or inside the

transformations

@busy-umbrella-36067 sorry no, I use

dependsOn

in a following

ComponentResource

of mine which depends on the database helm chart to be fully up&running

ah, so your component starts creating even though you have it set to depend on the chart

correct

I would look around accessing individual resources of a helm chart

The chart is in another

ComponentResource

to be precise. I tried to depends on this “container” and also directly on the chart inside itself, both failed.

The other thing I can think of is a

Job

which loops until your DB is reachable.

I think I can do that, but that’s tedious, I had hope pulumi should be “smart” to understand the

ComponentResource

and

Chart

dependencies. I’ll try that

Agreed, its not ideal (I would call it jank) Thats why I would research on how to access one of the 10+ resources the chart creates instead of the whole chart before I go with the

Job

@busy-umbrella-36067 there’s a

chart.getResource()

method, trying right now

This feature is tracked in https://github.com/pulumi/pulumi-kubernetes/issues/861

Nice, this might also be helpful if you wanna just depend on your component resource https://www.pulumi.com/docs/intro/concepts/programming-model/#registering-component-outputs You could register the resource you get from

chart.getResource()

as an output and that way all you would need to

dependsOn

is your first component

The call to registerOutputs also tells Pulumi that the resource is done registering children and should be considered fully constructed, so—although it's not enforced—the best practice is to call it in all components even if no outputs need to be registered.

@busy-umbrella-36067 right ! I forgot about that. I can confirm using

getResource()

works and my component holds until the database services are up. Will try the cleaner way with

registerOutputs()

right away

not sure that would help and I actually does not really have a direct input from the chart, so that would make things more messy. But that could maybe trigger a dependency in some other cases.