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

looks like `k8s.yaml.ConfigFile` is a `CollectionComponentResource`.. is that not an acceptable “Resource” to pass as a value for `dependsOn`?

hmmm maybe i should be passing `dependsOn: foo.resources`

well.. that doesn’t compile, but im gonna try `dependsOn: foo.resources.apply((m) =&gt; Object.values(m))`
seems overly complex for a seemingly common use-case, but let’s see

This problem might be more widespread than just with Configfile. I have the same issue when I have a resource depend on a helm chart. The resource will be applied before the helm chart deployment is fully complete

thanks for the data point!

are you passing `dependsOn: chart` or `dependsOn: chart.resources.apply((m) =&gt; Object.values(m))`?

i just tried the `.resources.apply(…)` approach and it seems to have worked

it would be nice if pulumi auto-expanded CollectionResources though..

interesting! i was just passing the `chart` variable

This is the same underlying issue as <https://github.com/pulumi/pulumi-kubernetes/issues/861> This affects the YAML and Helm SDKs, and we’re currently working on a fix.