New Resource: aws_glue_connection

[bflad]

Closes #3874

make testacc TEST=./aws TESTARGS='-run=TestAccAWSGlueConnection'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -run=TestAccAWSGlueConnection -timeout 120m
=== RUN   TestAccAWSGlueConnection_Basic
--- PASS: TestAccAWSGlueConnection_Basic (12.92s)
=== RUN   TestAccAWSGlueConnection_Description
--- PASS: TestAccAWSGlueConnection_Description (19.69s)
=== RUN   TestAccAWSGlueConnection_MatchCriteria
--- PASS: TestAccAWSGlueConnection_MatchCriteria (29.49s)
=== RUN   TestAccAWSGlueConnection_PhysicalConnectionRequirements
--- PASS: TestAccAWSGlueConnection_PhysicalConnectionRequirements (642.15s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	704.298s

[katbyte]

LGTM 👌

[bflad]

This has been released in version 1.15.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[glindholm]

Hi Brian, I'm trying to use the aws_glue_connection resource and having a problem.
I'm creating a Connection to a data source in private VPC subnet, specifically to RDS Aurora.
The Connection gets created but the AvailabiltyZone is not being set. I see that the AWS api docs state the AvailablityZone is not required (and deprecated and had not effect), however, if AvailabilityZone is not set then Test Connection or a Glue Job that tries to use the connection fails with Exception CONNECTION_LIST_CONNECTION_WITH_AZ_NULL.
I believe the AWS api docs is wrong, and have reported this to AWS.
When your Connection is into a private subnet then the AZ and subnet must be specified.
When you create a connection from the console it always sets the AvailabiltyZone, you can see this from the CLI (aws glue get-connections).
If I modify the connection Terraform creates and add the AvailabilityZone then the connection works correctly.

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