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

feat: support proxy and ssl #230

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

NguyenHoangSon96
Copy link
Contributor

@NguyenHoangSon96 NguyenHoangSon96 commented Mar 11, 2025

Closes #

Proposed Changes

Add proxy support for query api

Screenshot 2025-03-05 at 10 41 55

Checklist

  • CHANGELOG.md updated
  • Rebased/mergeable
  • A test has been added if appropriate
  • Tests pass
  • Commit messages are conventional
  • Sign CLA (if not already signed)

@NguyenHoangSon96 NguyenHoangSon96 self-assigned this Mar 11, 2025
Copy link

codecov bot commented Mar 12, 2025

Codecov Report

Attention: Patch coverage is 38.66667% with 46 lines in your changes missing coverage. Please review.

Project coverage is 86.29%. Comparing base (8db709b) to head (ec530c4).

Files with missing lines Patch % Lines
...m/influxdb/v3/client/internal/FlightSqlClient.java 25.49% 33 Missing and 5 partials ⚠️
...va/com/influxdb/v3/client/config/ClientConfig.java 68.42% 2 Missing and 4 partials ⚠️
...va/com/influxdb/v3/client/internal/RestClient.java 60.00% 0 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #230      +/-   ##
==========================================
- Coverage   89.71%   86.29%   -3.43%     
==========================================
  Files          18       18              
  Lines         963     1029      +66     
  Branches      150      159       +9     
==========================================
+ Hits          864      888      +24     
- Misses         39       73      +34     
- Partials       60       68       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@NguyenHoangSon96
Copy link
Contributor Author

Hi @bednar
Removed the test cases made codecove low
I will make it up after add Envoy to CI pipline

@NguyenHoangSon96 NguyenHoangSon96 requested a review from bednar March 12, 2025 11:09
Copy link
Contributor

@karel-rehor karel-rehor left a comment

Choose a reason for hiding this comment

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

Still in progress. But I've raised a couple of questions in the config file.

I was surprised to see that io.grpc.netty.GrpcSslContexts is tagged as @experimental and would not want to use "experimental" code in a public library. However, after digging around in https://github.com/grpc/grpc-java/blob/master/netty/src/main/java/io/grpc/netty/GrpcSslContexts.java I see that it has been experimental for 9 years... 😕

TBC

private final Authenticator authenticator;
private final Map<String, String> headers;
private final SslContext grpcSslContext;
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see either grpcSslContext or sslContext in the Javadoc above the class.

@@ -97,8 +102,11 @@ public final class ClientConfig {
private final Boolean allowHttpRedirects;
private final Boolean disableServerCertificateValidation;
private final ProxySelector proxy;
private final ProxyDetector queryApiProxy;
Copy link
Contributor

Choose a reason for hiding this comment

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

This self-descriptive naming might be more precise as grpcApiProxy or grpcProxy. It would also match with the grpcSslContext naming below.

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.

2 participants