This message was deleted.

It seems to only wait for the chart itself to register, not for all of the sub resources. Instead, it should wait for the full chart to complete

Yes - currently

dependsOn: component

does not implicitly depend on it's children. We are considering giving it that semantic as part of https://github.com/pulumi/pulumi/issues/1743.

Thanks for the update.

It should be possible to construct the dependencies on all of the child resources manually today from

.resources

- but it's a little hairy at the moment.

They’re also created by a few jobs, not even necessarily directly.

Actually - I haven't tried yet - but does this work:

{ dependsOn: chart.resources.apply(o => Object.values(o)) }

I’ll give it a shot!

for cert-manager i was able to do

const dependsOn = certManager.resources.apply(resources => Object.keys(resources).map(key => resources[key]));

Output<CustomResource[]> must have a [Symbol.iterator]() method

You can do:

{ dependsOn: c.resources.apply(o => [someOtherResource, ...Object.values(o)]) }

(i had the same problem with cert-manager, and that fixed the problems i was having)

No more type errors @white-balloon-205

@bitter-dentist-28132 Yep - your code is morally doing the exact same thing - so great to hear that that did work for you! Note that

Object.values(o)

is just a slightly easier way to accomplish

Object.keys(o).map(key => o[key])

.

yup, i know, not sure why i didn't do

Object.values

there

this is a fundamental problem with the way helm works, and the way istio attempts to get around it.