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

[New Data Source]: aws_elasticache_subnet_group #27114

Closed
posquit0 opened this issue Oct 5, 2022 · 4 comments · Fixed by #27233
Closed

[New Data Source]: aws_elasticache_subnet_group #27114

posquit0 opened this issue Oct 5, 2022 · 4 comments · Fixed by #27233
Labels
new-data-source Introduces a new data source. service/elasticache Issues and PRs that pertain to the elasticache service.
Milestone

Comments

@posquit0
Copy link
Contributor

posquit0 commented Oct 5, 2022

Description

image

Other similar subnet group resources also provide data sources. A data source for the subnet group is required to find the vpc id with the subnet group name.

Requested Resource(s) and/or Data Source(s)

  • aws_elasticache_subnet_group

Potential Terraform Configuration

data "aws_elasticache_subnet_group" "this" {
  name = "default"
}

resource "aws_security_group" "this" {
  name        = "example"
  description = "Example Security Group."
  vpc_id      = data.aws_elasticache_subnet_group.this.vpc_id
}

References

https://docs.aws.amazon.com/cli/latest/reference/elasticache/describe-cache-subnet-groups.html

Would you like to implement a fix?

No

@posquit0 posquit0 added the needs-triage Waiting for first response or review from a maintainer. label Oct 5, 2022
@github-actions github-actions bot added service/elasticache Issues and PRs that pertain to the elasticache service. service/vpc Issues and PRs that pertain to the vpc service. labels Oct 5, 2022
@github-actions
Copy link

github-actions bot commented Oct 5, 2022

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@bschaatsbergen
Copy link
Member

bschaatsbergen commented Oct 10, 2022

Hi @posquit0, thanks for raising this issue. I'm happy to work on this in the coming few days.

@ewbankkit ewbankkit added new-data-source Introduces a new data source. and removed needs-triage Waiting for first response or review from a maintainer. service/vpc Issues and PRs that pertain to the vpc service. labels Oct 13, 2022
@github-actions github-actions bot added this to the v4.36.0 milestone Oct 17, 2022
@github-actions
Copy link

This functionality has been released in v4.36.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-data-source Introduces a new data source. 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