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

Is there a way to ignore changes to resourceName?   When I create instance templates, I want the name to have a timestamp in it.  But that triggers an update.

This does not work:

`opts=ResourceOptions(ignore_changes=["resourceName"])`

Wonder if setting the “name” would be a better approach?

I'm not entirely sure what you're after, but by `resourceName` do you mean
```new SomeResource("this part?")```


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?

Just in case: <https://www.pulumi.com/docs/concepts/options/aliases/>

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?

I want the timestamp so it’s blatantly obvious if  an instance is using an old one.

Looks like setting name (not resourceName) works!  I also append a random element at the end for uniqueness (which Pulumi would do otherwise).

`opts=ResourceOptions(ignore_changes=["name"]),  # Avoid changes due to datestamp and random`

With a bit more testing, this looks to not be a great solution.

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.