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.

Pulumi Community

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

<@U01KRRFFRFW> 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

<@U01TTG4G6KA> that’s what I was after. I thought I’d seen something like this before

<@UCWG26BH7> I’ve done similar for the actual Kubernetes deploys (SHA or timestamp), but I was looking for Pulumi feature

Something that actually recreates the resource

<@UCWG26BH7> 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.