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

[resty.resolver] try to resolve upstream peers #478

Merged
merged 2 commits into from
Nov 15, 2017
Merged

Conversation

mikz
Copy link
Contributor

@mikz mikz commented Nov 14, 2017

  • defining an upstream can be used as a shortcut to skip DNS resolution
  • if an upstream is defined with the same name then use the peers

extracted from #474

return nil, err
end

for i=1, #peers do
Copy link
Contributor

Choose a reason for hiding this comment

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

According to the if above, here we could have peers = nil, and then #peers would raise an error.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

True that is possible. Will change the condition to return when there are no peers.

@mikz mikz force-pushed the resolver-upstream branch 2 times, most recently from eb4727f to f558e4f Compare November 15, 2017 10:05
@mikz mikz requested a review from davidor November 15, 2017 10:06
* defining an upstream can be used as a shortcut to skip DNS resolution
* if an upstream is defined with the same name then use the peers
@davidor davidor merged commit 5b854f8 into master Nov 15, 2017
@davidor davidor deleted the resolver-upstream branch November 15, 2017 10:26
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