faint-motherboard-9543805/18/2020, 10:13 PM
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
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 ?
busy-umbrella-3606705/18/2020, 10:15 PM
to the chart or inside the
faint-motherboard-9543805/18/2020, 10:16 PM
in a following
of mine which depends on the database helm chart to be fully up&running
busy-umbrella-3606705/18/2020, 10:18 PM
faint-motherboard-9543805/18/2020, 10:18 PM
busy-umbrella-3606705/18/2020, 10:19 PM
faint-motherboard-9543805/18/2020, 10:19 PM
to be precise. I tried to depends on this “container” and also directly on the chart inside itself, both failed.
busy-umbrella-3606705/18/2020, 10:20 PM
which loops until your DB is reachable.
faint-motherboard-9543805/18/2020, 10:21 PM
dependencies. I’ll try that
, will have a look, but that’s kind of “dirty” workaround I guess
busy-umbrella-3606705/18/2020, 10:22 PM
faint-motherboard-9543805/18/2020, 10:28 PM
method, trying right now
gorgeous-egg-1692705/18/2020, 10:29 PM
busy-umbrella-3606705/18/2020, 10:30 PM
as an output and that way all you would need to
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.
faint-motherboard-9543805/18/2020, 10:34 PM
works and my component holds until the database services are up. Will try the cleaner way with
and directly depending on the resource(s) needed in
works, registering the same resource(s) in
and only using the top
as a dependency unfortunately does not work as expected. I’ll stick to direct references the resources I need to wait for, for now. Thanks for your help !
busy-umbrella-3606705/18/2020, 10:42 PM
faint-motherboard-9543805/18/2020, 10:44 PM