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

Hello everyone! I just got hit with this bug: <https://github.com/pulumi/pulumi/issues/6272> anyone knows of a workaround / fix? couldn't find any solution online so far, and that kind of breaks our setup :melting_face:

This is a total hack and I haven't tested if it actually works as a workaround, and even if it did work it's not something I'd recommend, but:

What if you make the value you want to ignore a Stack Output and instead of using IgnoreChanges, you have a ternary that computes "if this should be ignored, instead use value from the Stack Output from this Stack itself (self-referential StackReferences are possible), but otherwise use the new computed value.

wooow, I'd never think of that. But even if it works, I don't think it's very practical - we have ~30 resources being affected by this, hahah