This message was deleted.
# generals
sparse-intern-71089
09/10/2019, 8:56 PMThis message was deleted.
c
cool-egg-852
09/10/2019, 9:22 PMFigured 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)
cool-egg-852
09/11/2019, 12:31 PMOk, so even in an properly configured one I am experiencing this.
cool-egg-852
09/11/2019, 12:32 PM@white-balloon-205 this occurs with the
{ dependsOn: c.resources.apply(o => [someOtherResource, ...Object.values(o)]) }cool-egg-852
09/11/2019, 12:41 PMLooks like the order may matter there. Have to do
someOtherResourcew
white-balloon-205
09/11/2019, 1:09 PM
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
cool-egg-852
09/11/2019, 1:11 PMAny 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.
cool-egg-852
09/11/2019, 1:13 PMI 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]) });cool-egg-852
09/11/2019, 1:14 PMLike that should be enough to cause it, obviously it’s not really testable I just wrote up a quick example.
cool-egg-852
09/11/2019, 2:21 PMOk, so that must not be it
cool-egg-852
09/11/2019, 7:30 PMAny ideas?
cool-egg-852
09/18/2019, 11:00 AMSo what I gather is that it’s because the helm chart resources aren’t known at the time, and therefore it fails.