provider/aws: expose Route 53 zone nameservers

[catsby]

🚧
This PR attempts to expose the NS elements of Route 53 zone. Refs #462

[mitchellh]

Debug line!

[catsby]

🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧

[mitchellh]

LGTM. It might be nice to add to the acceptance tests as well.

[catsby]

Example config for proof of concept:

provider "aws" {
   region = "us-west-2"
}

resource "aws_route53_zone" "main" {
    name = "notexample.com"
}

resource "aws_route53_record" "default" {
    zone_id = "${aws_route53_zone.main.zone_id}"
    name = "www.notexample.com"
    type = "A"
    ttl = "30"
    records = ["127.0.0.1"]
}

resource "aws_instance" "default" {
  ami = "ami-9fc29baf"
  instance_type = "t1.micro"
  tags {
    Name = "testing-user-data-things"
    TestData = "${aws_route53_zone.main.nameservers.1}"
  }
}

I believe this is blocked by #1215 though

[phinze]

This seems AOK - just needs an acceptance test line added to cover us for this attribute.

[catsby]

I'll revisit this when #1215 is resolved

[catsby]

close in favor of #1525

[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.