Skip to content

Conversation

@sergiyvamz
Copy link
Contributor

Summary

add support of RDS Proxy custom endpoints

Additional Reviewers

@karenc-bq
@aaron-congo
@sophia-bq

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Comment on lines +428 to +429
} else if (isRdsProxyEndpointDns(host)) {
return RdsUrlType.RDS_PROXY_ENDPOINT;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious why do we need these? Do the existing isRdsProxyDns and RDS_PROXY not cover the same cases? Could we remove one of these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of our plugins are not compatible with RDS Proxy so it's important to properly recognize all type of urls related to RDS Proxy. we can reuse the same RDS_PROXY but I think it's better to be precise.

@sergiyvamz sergiyvamz force-pushed the feat-rds-proxy-endpoints branch from 04ad6c1 to e12ca0a Compare October 30, 2025 00:20
@sergiyvamz sergiyvamz merged commit 39a589b into main-3.x Oct 30, 2025
3 checks passed
@sergiyvamz sergiyvamz deleted the feat-rds-proxy-endpoints branch October 30, 2025 01:02
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.

3 participants