Specify a custom dial function per config #1527
Conversation
WalkthroughThe recent updates introduce a significant enhancement in connection management by incorporating a configurable Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Status
Actionable comments generated: 2
Configuration used: CodeRabbit UI
Files selected for processing (2)
- connector.go (1 hunks)
- dsn.go (1 hunks)
Additional comments: 6
connector.go (3)
80-92: Please ensure to add tests that cover the new functionality introduced by the use of
c.cfg.DialFunc. This is crucial for verifying that the custom dial function works as expected and handles errors properly.80-92: Remember to update the documentation to include information about the new
DialFuncconfiguration option. This will help users understand how to use the new feature.80-92: If this is your first contribution to the project, please add yourself to the AUTHORS file as per the project's contribution guidelines.
dsn.go (3)
55-55: Verify whether the
DialFuncfield should be included in theFormatDSNmethod output. If it is intended to be part of the DSN string, appropriate handling needs to be added.55-55: Confirm that the
DialFuncfield does not need to be normalized within thenormalizemethod. If it does require normalization, appropriate logic should be added.55-55: Ensure that the
DialFuncfield does not need to be parsed from the DSN string in theparseDSNParamsfunction. If it should be included, parsing logic will need to be implemented.
connector.go
Outdated
| dctx, cancel = context.WithTimeout(ctx, c.cfg.Timeout) | ||
| defer cancel() | ||
| } | ||
| mc.netConn, err = c.cfg.DialFunc(dctx, mc.cfg.Addr) |
There was a problem hiding this comment.
There is a potential issue with error handling after the custom DialFunc is called. If an error occurs, it should be handled similarly to how it's handled after the global dial function or net.Dialer is called.
+ mc.netConn, err = c.cfg.DialFunc(dctx, mc.cfg.Addr)
+ if err != nil {
+ return nil, err
+ }Committable suggestion
❗ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| mc.netConn, err = c.cfg.DialFunc(dctx, mc.cfg.Addr) | |
| mc.netConn, err = c.cfg.DialFunc(dctx, mc.cfg.Addr) | |
| if err != nil { | |
| return nil, err | |
| } |
aaronjheng
force-pushed
the
dial-func
branch
from
df2bedf
to
ac7765c
Compare
There was a problem hiding this comment.
Review Status
Actionable comments generated: 3
Configuration used: CodeRabbit UI
Files selected for processing (2)
- connector.go (1 hunks)
- dsn.go (2 hunks)
Additional comments: 5
connector.go (1)
- 84-91: The implementation of the conditional dial function usage looks correct. It checks if a custom dial function is provided and uses it to establish a connection. If not, it falls back to the previously existing dialing mechanisms. This change aligns with the PR's objective to allow specifying a custom dial function for each configuration.
However, ensure that the custom
DialFuncis thoroughly tested, especially since the PR checklist indicates that tests for this new functionality are pending. It's important to cover various scenarios, including timeouts and error handling, to ensure the new dialing mechanism works as expected.dsn.go (4)
13-13: The import of the
contextpackage is appropriate given the newDialFuncfield in theConfigstruct.70-71: The addition of the
DialFuncfield to theConfigstruct enables per-configuration custom dial functions, which is a key objective of this PR.70-71: The function signature for
DialFuncis correct and follows the conventional pattern for dial functions in Go, taking acontext.Context, network type, and address, and returning anet.Connand an error.74-74: Verify if any normalization is required for the new
DialFuncfield within thenormalizemethod.
aaronjheng
force-pushed
the
dial-func
branch
from
ac7765c
to
2d38b27
Compare
aaronjheng
force-pushed
the
dial-func
branch
from
2d38b27
to
f0f5dd4
Compare
aaronjheng
force-pushed
the
dial-func
branch
from
f0f5dd4
to
31d874d
Compare
There was a problem hiding this comment.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files selected for processing (2)
- connector.go (1 hunks)
- dsn.go (1 hunks)
Additional comments: 3
connector.go (2)
- 90-97: The implementation of the custom
DialFuncusage within theConnectmethod is correctly checking ifDialFuncis provided and uses it if available. This approach allows for flexibility in establishing network connections, aligning with the PR's objectives. However, consider adding a comment explaining the purpose of the conditionalcontext.WithTimeoutcreation based onmc.cfg.Timeoutto clarify its intent for future maintainers.- 99-113: The fallback mechanism to use the default dialing method when
DialFuncis not provided is correctly implemented. However, there's a past comment bymethanesuggesting not to lookupdialswhenc.cfg.DialFunc != nil. This has been addressed by the conditional check forc.cfg.DialFuncat the beginning of this segment. It's good practice to ensure that unnecessary operations are avoided when a custom dial function is provided, enhancing performance and maintainability.dsn.go (1)
- 57-57: The addition of the
DialFuncfield to theConfigstruct is correctly implemented, allowing users to specify a custom dial function for connection establishment. This change effectively addresses the PR's objectives by enhancing flexibility in connection handling. It's important to ensure that documentation is updated to include information about this new field and how to use it, as it introduces a significant new capability for users.
| mc.parseTime = mc.cfg.ParseTime | ||
|
|
||
| // Connect to Server | ||
| dialsLock.RLock() | ||
| dial, ok := dials[mc.cfg.Net] | ||
| dialsLock.RUnlock() | ||
| if ok { | ||
| if c.cfg.DialFunc != nil { | ||
| dctx := ctx | ||
| if mc.cfg.Timeout > 0 { | ||
| var cancel context.CancelFunc | ||
| dctx, cancel = context.WithTimeout(ctx, c.cfg.Timeout) | ||
| defer cancel() | ||
| } | ||
| mc.netConn, err = dial(dctx, mc.cfg.Addr) | ||
| mc.netConn, err = c.cfg.DialFunc(dctx, mc.cfg.Net, mc.cfg.Addr) | ||
| } else { | ||
| nd := net.Dialer{Timeout: mc.cfg.Timeout} | ||
| mc.netConn, err = nd.DialContext(ctx, mc.cfg.Net, mc.cfg.Addr) | ||
| dialsLock.RLock() | ||
| dial, ok := dials[mc.cfg.Net] | ||
| dialsLock.RUnlock() | ||
| if ok { | ||
| dctx := ctx | ||
| if mc.cfg.Timeout > 0 { | ||
| var cancel context.CancelFunc | ||
| dctx, cancel = context.WithTimeout(ctx, c.cfg.Timeout) | ||
| defer cancel() | ||
| } | ||
| mc.netConn, err = dial(dctx, mc.cfg.Addr) | ||
| } else { | ||
| nd := net.Dialer{Timeout: mc.cfg.Timeout} | ||
| mc.netConn, err = nd.DialContext(ctx, mc.cfg.Net, mc.cfg.Addr) | ||
| } | ||
| } | ||
|
|
||
| if err != nil { |
There was a problem hiding this comment.
📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [175-179]
The TLS configuration used in the default and custom dial functions does not specify a minimum version. It's recommended to explicitly set the minimum TLS version to TLS 1.3 to ensure stronger security guarantees. Additionally, the use of InsecureSkipVerify: true in the skip-verify case should be carefully considered, as it disables TLS/SSL certificate verification, making the connection vulnerable to man-in-the-middle (MTM) attacks. This should only be used for debugging purposes and not in production environments.
- cfg.TLS = &tls.Config{InsecureSkipVerify: true}
+ cfg.TLS = &tls.Config{InsecureSkipVerify: true, MinVersion: tls.VersionTLS13}And for other relevant TLS configurations, ensure MinVersion: tls.VersionTLS13 is added.
Description
Specify a custom dial function per config instead of using RegisterDialContext. It's hard to bind different state infomation for dialing with
RegisterDialContext. Like SSH tunneling, if we want to use diffrent SSH connections, uniquenetfor RegisterDialContext is required If I'm not wrong.Use cases:
Config/dsnChecklist
Summary by CodeRabbit
connectorcomponent to support flexible connection establishment through a newDialFuncoption.Configstruct documentation to reflect the addition of theDialFuncfield, enabling more controlled connection processes.