https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
hard to say for sure, but I would be very surprised if this was a bug. my guess is that your resource definition really is different.
a
I extracted the secret and base64 decoded it to check it with the secret I'm replacing it with and they are the same.
I imagine I've missed something but I'll find out sooner or later when I delete the secret in production and replace it with the one that I think is the same 🙂
c
oh you know, I actually do think this could be a bug. the secret value might be choking the diff functionality. @microscopic-florist-22719?
a
It has to be exactly the same from a YAML perspective. I had this problem and I don't recall exactly what I did to make the yaml the same.
I don't think I was dealing with a secret though.
a
Yep, it's got to be the same ... but it does indeed seem to be the same. I've got an even more curious case of a batch/v1beta1 which was created from a Helm v2 chart. I'm trying to import it as a 
k8s.batch.v1batch.CronJob
. I've exported the cronjob with kubectl as JSON. I pasted the code into my TS file, wrapped it in a CronJob constructor and it will not import. It reckons that the 
metadata
has changed by adding a 
labels
object, and that the entire 
spec
object has been added. I can't see how this can be. It's certainly very surprising behaviour!
Open in Slack
PreviousNext
Powered by

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.

Powered by