-
Notifications
You must be signed in to change notification settings - Fork 4
feat: Support HTTP schemes #58
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
Conversation
jajeffries
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - I'm not sure if we class this as a breaking change due to the port change, but I think in practice people will almost always be specifying a port so it should be ok
Co-authored-by: Michal Fiedorowicz <mfiedorowicz@netboxlabs.com>
|
🎉 This PR is included in version 1.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This pull request updates the Diode SDK to support both gRPC and HTTP(S) connection schemes, improving flexibility for users. The main changes clarify usage in the documentation and enhance the connection parsing logic to handle more schemes and default ports.
Documentation improvements:
README.mdto explain thattargetcan usegrpc://,grpcs://,http://, orhttps://schemes, with examples for both insecure and secure connections.Connection parsing enhancements:
parse_targetinclient.pyto accepthttpandhttpsschemes in addition togrpcandgrpcs, and updated the error message accordingly.parse_targetto use:80forgrpcandhttp, and:443forgrpcsandhttps.grpcsandhttpsschemes.