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

[WIP] provider/aws: Availability Zone helper resource #6669

Closed
wants to merge 2 commits into from

Conversation

pgray
Copy link
Contributor

@pgray pgray commented May 14, 2016

This resource reads the availability zones available to your account and provides a way of passing them to other resources/modules.

Example config:

resource "aws_availability_zones" "test" {
  name = "test"
}
output "az1" {
  value = "${element(aws_availability_zones.test.availability_zones, 0)}"
}

I'm looking for feedback on whether other people think this would be valuable, and hopefully guidance on how to test this better.

I'm thinking that it could save people time/lines of configuration when it comes to modules and other resources you might want 1 or more of across all your availability zones.

@pgray pgray changed the title provider/aws: Availability Zone helper resource [WIP] provider/aws: Availability Zone helper resource May 14, 2016
@jen20
Copy link
Contributor

jen20 commented May 14, 2016

Hi @pgray! Thanks for opening a pull request! I completely agree that being able to get this kind of information from AWS is useful, and we definitely want to support it in Terraform. One thing we are currently working on is @apparentlymart's proposal of data resources in #4169 - the work is on PR #6598, which I am planning to review next week. With that in mind, I'm going to hold off merging this until that work is integrated - we will definitely implement this feature though!

@pgray
Copy link
Contributor Author

pgray commented May 14, 2016

Hey @jen20, thanks for the great feedback. I'll make sure to keep an eye on how things are going with that. I'd love to rework it once the changes are made to support data resources.

@jen20
Copy link
Contributor

jen20 commented May 14, 2016

Hi @pgray, I've implemented this as a data source in #6671 as part of the review process. I used your code from the Read method here almost verbatim, so thank you for the PR! I'll close this in favour of #6671 for now.

@jen20 jen20 closed this May 14, 2016
@vancluever
Copy link
Contributor

vancluever commented May 14, 2016 via email

@pgray
Copy link
Contributor Author

pgray commented May 14, 2016

Ahhhhhhh! Gotcha. Thanks all.

@ghost
Copy link

ghost commented Apr 25, 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 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants