provider/aws: add iam_server_certificate data source

[nicolai86]

this is useful e.g. when using lambda let's encrypt to generate IAM Server Certificates.

before this change you'd have to lookup the most recent certificate manually, e.g. using bash + variables. With this PR you can use a data source to do this automatically:

data "aws_iam_server_certificate" "my-domain" {
  name_prefix = "my-domain.org"
  latest = true
}

resource "aws_elb" "elb" {
  name = "my-domain-elb"

  listener {
    instance_port = 8000
    instance_protocol = "https"
    lb_port = 443
    lb_protocol = "https"
    ssl_certificate_id = "${data.aws_iam_server_certificate.my-domain.arn}"
  }
}

I've updated the documentation for this & also added unit- and integration tests for this:

make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSDataSourceIAMServerCertificate_basic'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /terraform/vendor/)
2016/12/06 20:39:34 Generated command/internal_plugin_list.go
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSDataSourceIAMServerCertificate_basic -timeout 120m
=== RUN   TestAccAWSDataSourceIAMServerCertificate_basic
--- PASS: TestAccAWSDataSourceIAMServerCertificate_basic (25.70s)
PASS
ok  	github.com/hashicorp/terraform/builtin/providers/aws	25.726s

[stack72]

LGTM! Thanks @nicolai86

% make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSDataSourceIAMServerCertificate_'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /terraform/vendor/)
2016/12/07 11:39:34 Generated command/internal_plugin_list.go
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSDataSourceIAMServerCertificate_ -timeout 120m
=== RUN   TestAccAWSDataSourceIAMServerCertificate_basic
--- PASS: TestAccAWSDataSourceIAMServerCertificate_basic (21.31s)
PASS
ok  	github.com/hashicorp/terraform/builtin/providers/aws	21.328s

[nicolai86]

Thanks @stack72 ❤️

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