aws_elasticache - add support for notification_topic_status

[toredash]

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

Currently the AWS provider does not support notification-topic-status, but it does support notification-topic-arn.

If a user manually disabled the topic arn from cli or AWS Console, terraform apply won't detect the change as the topic arn is defined, but is marked inactive in the API:

Requesting that aws_elasticache_cluster and aws_elasticache_replication_group is expanded to support notification-topic-status. API from AWS already supports this

New or Affected Resource(s)

• aws_elasticache_cluster
• aws_elasticache_replication_group

Potential Terraform Configuration

resource "aws_elasticache_cluster" "example" {
  cluster_id           = "cluster-example"
  engine               = "memcached"
  node_type            = "cache.m4.large"
  num_cache_nodes      = 2
  parameter_group_name = "default.memcached1.4"
  port                 = 11211
  notification_topic_arn = "arn:aws:sns:us-east-1:012345678999:my_sns_topic"
+  notification_topic_status = "active"

}

References

https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_ModifyCacheCluster.html https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_ModifyReplicationGroup.html

• NotificationTopicStatus

[github-actions[bot]]

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[bot]]

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.