Skip to content

Conversation

@MicahParks
Copy link
Contributor

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:

  • Updated the README.md to explain that target can use grpc://, grpcs://, http://, or https:// schemes, with examples for both insecure and secure connections.

Connection parsing enhancements:

  • Modified parse_target in client.py to accept http and https schemes in addition to grpc and grpcs, and updated the error message accordingly.
  • Adjusted the default port assignment in parse_target to use :80 for grpc and http, and :443 for grpcs and https.
  • Changed TLS verification logic to enable it for both grpcs and https schemes.

@github-actions
Copy link

github-actions bot commented Aug 8, 2025

Coverage

Coverage Report
FileStmtsMissCoverMissing
/opt/hostedtoolcache/Python/3.10.18/x64/lib/python3.10/site-packages/netboxlabs/diode/sdk
   client.py243797%105, 280, 340, 345, 349, 405, 433
TOTAL277797% 

Tests Skipped Failures Errors Time
96 0 💤 0 ❌ 0 🔥 1.142s ⏱️

@MicahParks MicahParks marked this pull request as ready for review August 8, 2025 15:49
Copy link
Contributor

@jajeffries jajeffries left a 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>
@MicahParks MicahParks merged commit e7fa366 into develop Aug 11, 2025
6 checks passed
@MicahParks MicahParks deleted the schemes-and-ports branch August 11, 2025 15:48
@MicahParks MicahParks changed the title Support HTTP schemes feat: Support HTTP schemes Aug 11, 2025
@github-actions
Copy link

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants