ElastiCache Tag Modification

[bondsb]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Provide tag modification support to AWS ElastiCache resources.

Support for tag modification has recently been updated in Go SDK version 1.38.15.

New or Affected Resource(s)

• aws_elasticache_*

Potential Terraform Configuration

resource "aws_elasticache_replication_group" "my_replication_group" {
  ...

  tags = {
    MyTagKey = "MyTagValue"
  }
}

References

• aws_elasticache_replication_group fails to add, modify, delete tags on existing resource  #1615
• Tags cannot be updated on redis aws_elasticache_replication_group resources #5366
• aws_elasticache_replication_group and tags #9002

[ewbankkit]

Requires:

• build(deps): Bump github.com/aws/aws-sdk-go from 1.38.12 to 1.38.16 #18702

[justinretzolk]

Hey @bondsb 👋 Thank you for taking the time to file this issue! It looks like a fix for this was released with v3.62.0 of the provider, specifically with this pull request.

Can you verify that with the newer version of the provider, you're no longer experiencing this issue?

[bondsb]

@justinretzolk Apologies for the delay.

That fix does not appear to work. v3.65.0 does not detect external tag changes and the result of a difference between actual tags and expected tags results in a plan with no changes.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.