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_alb_target_group data source #764

Closed
hashibot opened this issue Jun 13, 2017 · 3 comments
Closed

aws_alb_target_group data source #764

hashibot opened this issue Jun 13, 2017 · 3 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope.

Comments

@hashibot
Copy link

This issue was originally opened by @eheydrick as hashicorp/terraform#14420. It was migrated here as part of the provider split. The original body of the issue is below.


It would be great if there was an aws_alb_target_group data source. My use case is that I want to create a bunch of alb target groups and then create anaws_alb_listener_rule for each target group. That way I can create a single ALB that uses host based routing to target multiple services.

@hashibot hashibot added the enhancement Requests to existing resources that expand the functionality or scope. label Jun 13, 2017
@aharin
Copy link
Contributor

aharin commented Jun 30, 2017

It will be extremely useful to be able to get ARN or alb target group given its name. In the ECS context to assign a container to a classic elb only the name was required, however with alb one needs ARN of alb target group to register a container. Since ARN is not known up front, it would be very useful to query alb target group by name to find the ARN

stack72 pushed a commit that referenced this issue Jul 6, 2017
* Add aws_alb_target_group data source (#764)

* Fixed formatting issues

* Fixing type in docs
@stack72
Copy link
Contributor

stack72 commented Jul 6, 2017

Closed via #1037

@stack72 stack72 closed this as completed Jul 6, 2017
@ghost
Copy link

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

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
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.
Projects
None yet
Development

No branches or pull requests

3 participants