-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_elasticache_cluster does not export node endpoints or IP addresses #1918
Comments
This feels more like a bug - it's inconsistent with the behavior of other modules, it makes it impossible to use/address the elasticsearch clusters without manual intervention, and is currently a blocking issue for us, and I'm sure other shops as well... |
Apologies for not labeling correctly, I most likely just didn't grok the full issue here. I've relabeled it, and a PR was started to address this (#1965). Hopefully should get it in soon, thanks for the issue! |
Closing, this is implemented in #1965, can you check that out and update over there? |
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. |
(This is an issue for both memcache and redis cluster types - the example below is for redis)
Terraform 0.5.0
Sample configs:
Resulting elasticache_cluster in state - note no connection information:
Resulting entire state file:
The text was updated successfully, but these errors were encountered: