Add support for DescribeAvailabilityZones call

[rcostanzo]

Availability zones should be dynamically looked up and then referenced as variables vs. having to hard code them. This is available in the goamz library already and we just need the plumbing to expose the DescribeAvailabilityZonesResp object.

[mitchellh]

What are you referring to in this case? i.e. what would we be replacing with this?

[rcostanzo]

One example is I'd want to dynamically create subnets in each zone without having to hardcode the region's specific values (which are subject to change over time):

resource "aws_availability_zone" "my_zones" {
}

resource "aws_subnet" "my_subnet" {
  vpc_id = "ABC123"
  availability_zone = "${element(aws_availability_zone.my_zones.*.id, count.index)}"
  cidr_block = "192.168.x.x"
  count = "3"
}

Right now, I accomplish this by hard-coding a lookup in:

variable "zones" {
    default = {
        zone0 = "us-west-2a"
        zone1 = "us-west-2b"
        zone2 = "us-west-2c"
    }
}

Note that my example above depends on the #554 pull request.

[mitchellh]

LGTM. Tagged.

[phinze]

Hey there - we're consolidating Requests for AWS API Coverage over in the spreadsheet linked at #28 - head over there to record your username on what you'd like us to prioritize next!

[ghost]

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.