Add support for ConnectionType POSTGRESQL | AWS Glue Connections

[j-baillie]

Describe the feature

Please add support to programmatically create Connections in AWS Glue with the connection type POSTGRESQL. This functionality is available in the AWS GUI, but not through the API.
As such, such connections cannot be deployed with Terraform which relies on this SDK.

If these connection types are indeed supported on the backend (due to being able to ClickOps them together), why cannot they be supported in the public API?

Use Case

I need the function to be able to deploy POSTGRESQL connections in AWS Glue, with Terraform, for my Glue tasks.

Proposed Solution

I understand that the public API for AWS Glue does not currently support ConnectionType POSTGRESQL, due to its absence from the list of connection types noted here - ConnectionType.

Of course this functionality would need to be implemented on the public API, then into the SDK, then finally into the AWS Terraform provider.

Other Information

Such issues have also been posted on the AWS terraform provider - 41544

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Go SDK V2 Module Versions Used

github.com/aws/aws-sdk-go-v2/service/glue v1.121.0

Go version used

1.24.5

[lucix-aws]

The glue API you see in the SDK comes from the glue team's service model which they provide to us to generate our SDK. Evidently they have not updated their API model with this new information yet (they seem to have not updated it for a few things e.g. #3146).

We will upstream this to them.

[lucix-aws]

Also FYI if you're using the SDK directly you can just do types.ConnectionType("POSTGRESQL"). I recognize that if you're interacting with the API through Terraform it may not be possible to specify an arbitrary value like that.

[lucix-aws]

Upstreamed @ internal ref V1884972747

[Madrigal]

Discussed this internally.

The desired workflow from Glue is to use the types described in a call to ListConnectionTypes rather than from a published list, so ideally the validator from Terraform would not require the returning types to be available in the model, since they may not always be available in scenarios like this