This message was deleted.

sparse-intern-71089

11/08/2022, 8:57 PM

This message was deleted.

prehistoric-london-9917

11/08/2022, 9:02 PM

You could try making the chart depend on the node group using the ResourceOptions

prehistoric-london-9917

11/08/2022, 9:02 PM

Other people might have ideas in #CRFURDVQB too

brash-gigabyte-81569

11/08/2022, 9:03 PM

Yeah I tried that. Could be that the chart deleted but not in the order I wanted.

brash-gigabyte-81569

11/08/2022, 9:04 PM

I’ll ask there

billowy-army-68599

11/08/2022, 9:14 PM

in this case it’s likely the chart deleted but the subresources didn’t delete. It’s a tricky problem with helm releases 😞

brash-gigabyte-81569

11/08/2022, 9:15 PM

The only kinds of problems i find my self hitting

brash-gigabyte-81569

11/08/2022, 9:15 PM

brash-gigabyte-81569

11/08/2022, 9:16 PM

I did see that some providers have added some wait logic for instance the eks one waits on the cluster

billowy-army-68599

11/08/2022, 9:17 PM

you can wait inside an

apply

https://gist.github.com/lukehoban/fd0355ed5b82386bd89c0ffe2a3c916a it’s harder to do with a helm release

brash-gigabyte-81569

11/08/2022, 9:19 PM

i see

brash-gigabyte-81569

11/08/2022, 9:19 PM

i might give this a spin

brash-gigabyte-81569

12/02/2022, 6:53 PM

Future Searches: Found a better way by using this https://github.com/pulumi/pulumi-command

179 Views

Open in Slack

Previous Next

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.