Ignore changes for a single AWS Resource Tag

[emoshaya]

Is there a way to limit the @ignore_changes to just a single tag e.g. VERSION tag. As apposed to every single tag for a particular resource? I have a VERSION tag which is updated regularly by Jenkins and I would like a way to just ignore_changes for that tag.

Thanks

[dsolsona]

I'm also interested in this. ignore_changes = ["tags"] seems very generic and it appears that it also stops terraform adding new tags to resources.

[jen20]

Hi @emoshaya-cognito! There currently isn't a way to ignore changes to individual map fields. I don't believe there is a way to implement this given the current semantics of ignore_changes, though @phinze is more familiar with that area of the code base than I am.

[manojlds]

Would also like to have this. Use case - EBS volume tags are updated with the instance id of the instance in which they are mounted. Would like to control other tags from terraform, but ignore changes to the instance id tag.

[jimhoagland]

I would also like this. We run JanitorMonkey regularly, which adds CreatorId, CreatorName, PrincipalId. I really don't want those removed when doing an apply. Perhaps those can be listed in the config with some kind of marking that those tags should be ignored if present.

[pgporada]

This would be useful for us as well. Amongst other things we're doing is setting the current version of our application in the AWS console so people in there can check it without too much effort.

[ashald]

We would be glad to see this as well - we need to set a date-derived tags upon resource creation but the change in such tag shouldn't be a reason for resource "invalidation".

[nwalke]

We have an application that creates/updates/deletes tags on the resources it's running on, but have a set of tags that never get removed or updated. Would be super nice to ensure that group of tags never gets touched, but disregard the rest.

[joseph-holland]

Would also like this functionality.

[MikeMcMahon]

We do this already and it worked flawlessly in older versions of terraform (0.8.8 and prior)

ignore_changes {
  "tags.%",
  "tags.hostname",  # dynamically generated on boot time
   ...
}

However it seems that now it still seemingly ignores the individual tags (as it always has) but now for some reason in TF 0.9.11 it tries to re-apply the tags over and over and over and over and only seems to actually ignore the tag in the apply, not in the plan.