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 :slightly_smiling_face:

Is there a way of updating specific tags by using custom resources transformation (e.g username and timestamp, git sha) _only_ for resources that are actually going to be updated?

How would you add git sha as tags to updated resources _without_ applying new tag value to all existing resources in Pulumi deployment?

Not really doable at the moment, transformations are just run in the program as a pre-step to sending to the engine at the moment. But we are looking at over hauling how they work and this could be something that we look at supporting in the new system.

Hi Fraser! Thanks for the response :slightly_smiling_face: That’s what I assumed after reading all the docs I could find.

I wonder - let’s say that first I run `pulumi preview --save-plan=plan.json` and then during `pulumi up` I  read that json and only apply ‘dynamic value’ tags for the resources that have create/update in that plan. Would that work?

The only problem for me was that I couldn’t really figure out how, from code perspective, which Pulumi command is being executed, whether it was `preview` or `up` - I saw `Deployment.Instance.IsDryRun` could I use that?

Yup DryRun tells you if it's preview or not