This message was deleted.

I'm not entirely sure what you're after, but by

resourceName

do you mean

new SomeResource("this part?")

Yes.

ignoreChanges doesn't work here as you've found. You could use

aliases

for this purpose, but backing up a bit, what is the reasoning behind putting a timestamp in your resource name?

Aliases I don’t work as that won’t prevent a new resource from being created if only the resourceName changes. Also that keeps the old resource around and then list of aliases will get long and be dynamic. My use care is when a new resource needs to be made, it get’s the name with the timestamp, I don’t care what Pulumi calls it, but I care what I see in the cloud console. If I set “name”, could I ignore that?

ignore_changes simply tells Pulumi to ignore any changes to a particular field or set of fields. If you only want to track creation date,

name

is probably a decent approach, but it sounds like you want to track when a template was created and updated. And any time you update

name

you'll force a replacement. Tags are probably the only logical vehicle for what you're trying to get after, although not as visible as something like name.

Yup, neither name or resource_name work well. Rather than a tag, i can just look at the template and look at the creation date.