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

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>.

Currently without this istio may have troubles deploying in a single pass as the CRDs have to be created first, and they are in a separate helm chart.

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 =&gt; Object.values(o)) }
```

Hmm, problem is I can’t seem to have other dependencies. I tried `{ dependsOn: [...chart.resources.apply(o =&gt; Object.values(o)), someOtherResource] }` and got a type error

for cert-manager i was able to do
```
    const dependsOn = certManager.resources.apply(resources =&gt; Object.keys(resources).map(key =&gt; resources[key]));
```

Output&lt;CustomResource[]&gt; must have a [Symbol.iterator]() method

You can do:

```
{ dependsOn: c.resources.apply(o =&gt; [someOtherResource, ...Object.values(o)]) }
```

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

<@UM6PHB1RS> 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 =&gt; 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.

you don’t really have any good options until the lua lifecycle hooks are implemented.