Skip to content
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

fix: fix getCustomDomainInfo function to different APIGateway versions #537

Conversation

aalongkott
Copy link

Fixes #536
Description of Issue Fixed

  • Fix getCustomDomainInfo function to use different APIGateway versions according to endpointType and
    securityPolicy

Changes proposed in this pull request:

  • In getCustomDomainInfo function, using APIGateway version 1 when endpointType == "EDGE" and securityPolicy == "TLS_1_0". Otherwise, using APIGateway version 2.

@rddimon
Copy link
Collaborator

rddimon commented Jan 24, 2023

Hi @aalongkott

Thank you for your contribution!
Could you please also update unit tests?

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@aalongkott
Copy link
Author

aalongkott commented Jan 25, 2023

Hello @rddimon

I have fixed the unit tests according to the bugs. Please review and if the coverage does not match your requirements, please tell me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

getCustomDomainInfo does not work in Jakarta Region as APIGatewayV2 has not been supported in this region yet
2 participants