This message was deleted.

so your

nlb

call is running at the same time as your helm release call, because there’s no dependencies between them. The way to handle this is to use the

apply

callback mechanism. There’s an example here: https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/#query-kubernetes-resource-installed-by-helm-chart (pulumi interpolate is just syntactic sugar around

apply

It would work if inside

pulumi.interpolate

is an output from

export const release =...

, but in my case it is not an output, its a know predefined value If I specify something like this:

const nlb = aws.lb.getLoadBalancerOutput({
    name: pulumi.interpolate`${release.status}`,
});

It works, but it doesn't fit the needs. If I do something like this:

const nlb = aws.lb.getLoadBalancerOutput({
    name: pulumi.interpolate`${project}-${stack}`,
});
export const nlbDnsName = nlb.dnsName;

It return the same error Also, I tried to set LB name with values and use it as input, but with no luck: `pulumi.interpolate`${release.values.LbName}`,`

you need to use an output value from the release, if you can’t use interpolate, do something like:

const nlb = release.status.apply(status => ...)

@billowy-army-68599 thank you! it works 🙂