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

Add aws_elasticache_replication_group.reader_endpoint_address #15513

Closed
rquadling opened this issue Oct 6, 2020 · 3 comments
Closed

Add aws_elasticache_replication_group.reader_endpoint_address #15513

rquadling opened this issue Oct 6, 2020 · 3 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elasticache Issues and PRs that pertain to the elasticache service.

Comments

@rquadling
Copy link
Contributor

rquadling commented Oct 6, 2020

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

I want to provide read only access to the AWS Elasticache cluster in a way that I can already do for RDS. Get the "reader" endpoint, attach it to the DNS and job done. More or less.

With the current provider, the reader endpoint is not accessible.

aws describe-replication-groups --query='ReplicationGroups[0].NodeGroups[0].ReaderEndpoint.Address' is the current data that I want to get to.

New or Affected Resource(s)

  • aws_elasticache_replication_group (resource)
  • aws_elasticache_replication_group (data source)

Potential Terraform Configuration

Unsure what to put here.

References

@rquadling rquadling added the enhancement Requests to existing resources that expand the functionality or scope. label Oct 6, 2020
@ghost ghost added the service/elasticache Issues and PRs that pertain to the elasticache service. label Oct 6, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Oct 6, 2020
@anGie44 anGie44 removed the needs-triage Waiting for first response or review from a maintainer. label Oct 6, 2020
@rquadling
Copy link
Contributor Author

@anGie44 Is there a way to get some more eyes on this and get it merged/released? Happy to do more work on it if it is required.

@gdavison
Copy link
Contributor

gdavison commented Jan 5, 2021

This is a duplicate of #10519, which was resolved with PR #9979

@gdavison gdavison closed this as completed Jan 5, 2021
@ghost
Copy link

ghost commented Feb 5, 2021

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Feb 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elasticache Issues and PRs that pertain to the elasticache service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants