-
Notifications
You must be signed in to change notification settings - Fork 187
move to per-shard trillian client manager #2564
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
Signed-off-by: Bob Callaway <bcallaway@google.com>
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2564 +/- ##
===========================================
- Coverage 66.46% 24.99% -41.47%
===========================================
Files 92 190 +98
Lines 9258 24500 +15242
===========================================
- Hits 6153 6123 -30
- Misses 2359 17595 +15236
- Partials 746 782 +36
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Bob Callaway <bcallaway@google.com>
Signed-off-by: Bob Callaway <bcallaway@google.com>
Signed-off-by: Bob Callaway <bcallaway@google.com>
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.
Looks good overall! As long as we thoroughly test this against both active and inactive shards, seems good.
Signed-off-by: Bob Callaway <bcallaway@google.com>
Signed-off-by: Bob Callaway <bobcallaway@users.noreply.github.com>
this allows users to configure a different trillian gRPC backend per-shard instead of assuming all shards are hosted by the same trillian instance. It is backwards compatible (if only the base level values for
trillian-log-server.{address, port, tls, tls_ca_cert}
are specified, they are used for all shards unless overridden in the shard config).include some other minor fixes: