-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement]: Add AZURESQL to Glue Connection Type #37233
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This is a bit of a strange issue. The AWS API and downstream client docs all indicate that only several connection types are supported when I can see 21 in the AWS Management Console. When I create an Azure SQL connection in the console, CloudTrail shows that it is passing |
Here's an update after going back and forth with AWS support for two weeks. Basically they confirmed that the list of supported values for
AWS is still working on updating the documentation, however I am less confident about them triggering the downstream updates to the SDKs. The support person seems to be evasive with my questions on getting someone to fix the SDKs as well. Since the resource code is validating against the enum, we can either wait or manually append these values to a slice to at least add the support. That should be easy enough, however acceptance tests will be difficult as it involves third-party solutions. @justinretzolk, wonder if you could weigh in and see what the best approach is with dealing with this issue. Meanwhile I'll continue to push to get an answer on downstream SDK updates with the proper values. |
@acwwat - Thank you so much for putting so much effort in! |
Additional back-and-forth with AWS support has not been productive and I was basically told to talk to my account manager because AWS support does not have access to product roadmaps. They won't even acknowledge that they've communicated the need to update the downstream SDKs, so I will take that as a no... Instead of punishing end-users for this bug, I've decided to just work around the problem by adding the supported values and cross checking with the API requests from creating the connections in the Console. Will be submitting a PR shortly. |
Terraform Core Version
1.5.6
AWS Provider Version
5.47.0
Affected Resource(s)
Expected Behavior
Accepts all allowed connection types
Actual Behavior
Does not allow AZURESQL connection type
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Use AZURESQL as the connection_type
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: