-
Notifications
You must be signed in to change notification settings - Fork 617
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
Return error if ports are specified in dnsrr mode #1207
Conversation
We discussed this through slack with @mavenugo |
Current coverage is 54.97% (diff: 100%)@@ master #1207 diff @@
==========================================
Files 77 77
Lines 12257 12259 +2
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
- Hits 6744 6739 -5
- Misses 4591 4593 +2
- Partials 922 927 +5
|
}, | ||
}, | ||
}) | ||
assert.Error(t, err) |
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.
Check that the error contains ports can't be used with dnsrr mode
.
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.
I don't see that other tests validate error messages. I've seen this though
assert.Equal(t, codes.InvalidArgument, grpc.Code(err))
Should I add that check as well?
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.
Sure.
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
@aaronlehmann done. |
LGTM |
1 similar comment
LGTM |
@marcosnils |
@mrjana Given that routing-mesh performs opinionated port-based LB & it is not a generic network to be used for other purposes, I think we should remove this restriction & let the user use DNS-RR for back-end networks. wdyt ? |
Signed-off-by: Marcos Lilljedahl marcosnils@gmail.com