Hello 🙂 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 🙂 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?

Yup DryRun tells you if it's preview or not