Hello! 👋 I’m trying to automate our db migrations execution using Pulumi + Kubernetes. So far, i’ve tried to do it using two approaches: 1. Creating a k8s job that runs into completation, but both Pulumi and Kubernetes doesn’t have a resource lifecycle feature, like “delete this job after completion”. 2. By changing the image or name of the job. Since both fields are immutable, Pulumi should recreate the resource, but that’s not the case 😬.

Job.batch "api-migration-job-zdq5ov6o" is invalid: spec.template: Invalid value: [job spec]: field is immutable

I’ve tried to look at the

@pulumi/kubernetes

source code, but seems like it’s generated automatically. In this case, how do we fix that? 🤔

that’s a bug.

Sorry, i thought change detection was from the Terraform Kubernetes provider or something like that.

we don’t use TF for k8s.

Great to know! Now i understand why it’s so good 🙂 Can you help me to figure out where the change detection source code lives in?

yes.

Thanks!

@most-pager-38056 https://github.com/pulumi/pulumi-kubernetes/blob/master/pkg/provider/diff.go#L108

That’s beatiful. I’m going to create a PR right now 🙂

hmm

Hm, i thought the expression was

[*]

because it’s used here: https://github.com/pulumi/pulumi-kubernetes/blob/master/pkg/provider/diff.go#L87

I think it is?

Yep! Looks like it is: https://goessner.net/articles/JsonPath/

just responded. 🙂