https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
Figured it out. It’s breaking when using dependsOn with a helm chart that doesn’t know all the values (most likely because the helm chart is misconfigured)
Ok, so even in an properly configured one I am experiencing this.
@white-balloon-205 this occurs with the 
{ dependsOn: c.resources.apply(o => [someOtherResource, ...Object.values(o)]) }
that you gave me in the other thread the other day.
Looks like the order may matter there. Have to do 
someOtherResource
first. I’ll test that out in another cluster later today probably.
w
Hmm - that is surprising, and I don’t think I have a full picture of the repro here. If you can share a small code snippet - would love to investigate
c
Any helm chart caused this. Seems like you just can’t have the dependencies first in the array, not sure why. I’ll confirm this is the case though in a little bit.
I can test in another branch, I’m just in the middle of an upgrade so I can’t test it this second.
Copy code
const chart = new k8s.helm.v2.Chart('someChart');
const someOtherResource new k8s.core.v1.Service('for-example');
new k8s.core.v1.Service('use-this-one-for-depends', {}. {},{ dependsOn: chart.resources.apply(o => [ ...Object.values(o), someOtherResource]) });
Like that should be enough to cause it, obviously it’s not really testable I just wrote up a quick example.
Ok, so that must not be it
Any ideas?
So what I gather is that it’s because the helm chart resources aren’t known at the time, and therefore it fails.
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by