New Data Source: aws_lambda_function

[ian-d]

Resolves #2578.

Took a stab at creating the new aws_lambda_function data source. The qualifier property is a bit weird, but it's because of the way the AWS SDK handles it. If you supply an alias you get the actual version number back as Version. If you supply nothing you get $LATEST. So the resulting version property of the data source may end up being a version number or $LATEST.

make testacc TEST=./aws TESTARGS='-run=TestAccDataSourceLambdaFunction'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -run=TestAccDataSourceLambdaFunction -timeout 120m
=== RUN   TestAccDataSourceLambdaFunction_basic
--- PASS: TestAccDataSourceLambdaFunction_basic (37.71s)
=== RUN   TestAccDataSourceLambdaFunction_alias
--- PASS: TestAccDataSourceLambdaFunction_alias (35.50s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	73.246s

[ian-d]

Updated test runs from 45aae05.

make testacc TEST=./aws TESTARGS='-run=TestAccDataSourceLambdaFunction'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -run=TestAccDataSourceLambdaFunction -timeout 120m
=== RUN   TestAccDataSourceLambdaFunction_basic
--- PASS: TestAccDataSourceLambdaFunction_basic (36.52s)
=== RUN   TestAccDataSourceLambdaFunction_alias
--- PASS: TestAccDataSourceLambdaFunction_alias (35.09s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	71.648s

[ian-d]

Closing, #2984 is a much better implementation.

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