Adding configuration endpoint to the elasticache cluster nodes

[stack72]

@phinze This should add the functionality for #3149

When I run this against my own production cluster, I get the following:

[phinze]

@stack72 I think that ConfigurationEndpoint is a property of the CacheCluster, not of a CacheNode, no? Idea is to be able to auto-discover the node list in supported clients.

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

[stack72]

AH! Configuration_endpoint is for memcached only :)

I will change where it sits and run another test to make sure

[stack72]

@phinze ok, so I have now got this in the AWS console:

The terraform output gives me the following:

resource "aws_elasticache_cluster" "test_memcached" {
    cluster_id = "example"
    engine = "memcached"
    node_type = "cache.m1.small"
    port = 11211
    num_cache_nodes = 1
    parameter_group_name = "default.memcached1.4"
}

output "sample_configuration_endpoint" {
   value = "${aws_elasticache_cluster.test_memcached.configuration_endpoint}"
}

Outputs:
  sample_configuration_endpoint = example.lpokkm.cfg.euw1.cache.amazonaws.com:11211

[stack72]

@phinze I think this is now what you wanted?

[phinze]

Looks good - thank you!

[ghost]

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.