This message was deleted.

sparse-intern-71089

05/26/2021, 1:26 PM

This message was deleted.

glamorous-australia-21342

05/26/2021, 2:18 PM

How about this? https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/#CustomResourceOptions-deleteBeforeReplace

billowy-army-68599

05/26/2021, 3:44 PM

@lemon-monkey-228 a common practice here is to calculate the MD5 of the data you want to force a reload, and then set that as an env var in the Kubernetes deployment etc

lemon-monkey-228

05/26/2021, 8:36 PM

@glamorous-australia-21342 that’s what I was after. I thought I’d seen something like this before

🙌 1

lemon-monkey-228

05/26/2021, 8:36 PM

@billowy-army-68599 I’ve done similar for the actual Kubernetes deploys (SHA or timestamp), but I was looking for Pulumi feature

lemon-monkey-228

05/26/2021, 8:36 PM

Something that actually recreates the resource

bored-table-20691

05/28/2021, 3:55 AM

@billowy-army-68599 to give another example where I’ve found this to be necessary: I have an Job that happened to fail through its allowed retries, so it was baiscally stuck. If I did

pulumi up

, it would give an error from the kube API saying the job has failed too many times. The only recourse was to delete the job manually and run

pulumi refresh

to sync up the state.

4 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.