sparse-intern-71089
03/10/2023, 5:03 PMbillowy-army-68599
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
freezing-twilight-25806
03/10/2023, 6:55 PMpulumi.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}`,`billowy-army-68599
const nlb = release.status.apply(status => ...)
freezing-twilight-25806
03/13/2023, 8:43 AMNo 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