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.

Sign up for GitHub

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

Jump to bottom

bug: upstream_id in stream_route is ineffective. #4111

Closed
tokers opened this issue Apr 22, 2021 · 0 comments · Fixed by #4121
Closed

bug: upstream_id in stream_route is ineffective. #4111

tokers opened this issue Apr 22, 2021 · 0 comments · Fixed by #4121
Labels
bug Something isn't working

Comments

@tokers
Copy link
Contributor

tokers commented Apr 22, 2021 •
edited
Loading

Issue description

Although we can set upstream_id to stream_route, it's not really used during the process.

Environment

  • apisix version (cmd: apisix version): master branch: 86e4983
  • OS (cmd: uname -a):
  • OpenResty / Nginx version (cmd: nginx -V or openresty -V):
  • etcd version, if have (cmd: run curl http://127.0.0.1:9090/v1/server_info to get the info from server-info API):
  • apisix-dashboard version, if have:
  • luarocks version, if the issue is about installation (cmd: luarocks --version):

Minimal test code / Steps to reproduce the issue

What's the actual result? (including assertion message & call stack if applicable)

What's the expected result?
@tokers tokers added the bug Something isn't working label Apr 22, 2021
@tokers tokers linked a pull request Apr 24, 2021 that will close this issue
feat: support to use upstream_id in stream_route #4121
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: support to use upstream_id in stream_route tokers/apisix
1 participant
@tokers