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

Would it be possible to have the option of accessing the old value of a Stash?

We currently have a custom component that does this, due to stack references being very slow. But would love to see this natively supported :heart:

I don't think this is simple to do. Stash's are "replaced" not "updated" so the system doesn't propagate the old values to where new values are determined.

Also some compat issues here because SDKs aren't tied to engine versions, so the new SDK would declare the field oldOutput but if you run against an old engine it would never fill it in

Ah, so maybe an other component that does something like this?

Our current component code is:
<https://gist.github.com/UnderKoen/0090ea8a0e723029f86494167e4e434f>

I looked at the stash PR but I think it is outside my (non-existing) GO knowlegde to write all tests and structure like the pulumi repo has

We could copy that resource, but that's updating on each deploy right? So it's not quite the same as stash that only changes value when the trigger is set

Maybe raise an issue so it can be discussed and voted on by others as well

do you have the issue <@U087V5FT5D2> or <@U02J3T6A8LB>? i didn't see this before and i think this would also work for <https://pulumi-community.slack.com/archives/C84L4E3N1/p1780522633630489|https://pulumi-community.slack.com/archives/C84L4E3N1/p1780522633630489>