Skip to content
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 doesn't document cache_nodes #2272

Closed
nevir opened this issue Jun 8, 2015 · 6 comments · Fixed by #2332
Closed

aws_elasticache_cluster doesn't document cache_nodes #2272

nevir opened this issue Jun 8, 2015 · 6 comments · Fixed by #2332

Comments

@nevir
Copy link
Contributor

nevir commented Jun 8, 2015

It's tough to use aws_elasticache_cluster right now, since it doesn't expose the endpoint hostname for nodes in the cluster (maybe via an endpoint or endpoints attribute?)

@nevir
Copy link
Contributor Author

nevir commented Jun 8, 2015

Oh, it does expose cache_nodes; just not documented!

@nevir nevir changed the title aws_elasticache_cluster doesn't expose endpoints aws_elasticache_cluster doesn't document cache_nodes Jun 8, 2015
@juniorplenty
Copy link

@navir Nb: #2051 (That is still an issue in 1.5.2/3, even though it's closed in GH)

@nevir
Copy link
Contributor Author

nevir commented Jun 9, 2015

ah, fun :(

@mikeyhill
Copy link

Trying to create a Redis cluster with 2 nodes I get:

Error creating Elasticache: InvalidParameterValue: Cannot create a Redis cluster with a NumCacheNodes parameter greater than 1.
status code: 400,

However the cluster is created fine.


I'm currently on the latest master (dd24b58), however not sure which version that is - TF seems to be reporting version 0.6.0 for some unknown reason.

@radeksimko
Copy link
Member

Thanks for the report.
See #2332

@ghost
Copy link

ghost commented Apr 16, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants