-
Notifications
You must be signed in to change notification settings - Fork 25
[Relayminer][Follow-up] add forward capabilities to send request to suppliers #1681
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
base: main
Are you sure you want to change the base?
Conversation
…est request & websocket request
0438728 to
b9c72b9
Compare
|
Ping @bryanchriswhite 👋🏾 |
|
@jorgecuesta If you have some spare cycles, I'd really appreciate your thoughts/feedback/input on this feature! I've personally done a few rounds of review on the previous implementation of this, but am looking for a Supplier's perspective in terms of the product/feature. |
I can take a look on this into the weekend or Monday since I'm currently OOO right now. |
Summary
This PR aims to add capabilities to forward requests to HTTP and a WebSocket server in the relayminer.
It sets up a configurable authenticated endpoint (/services/{service_id}/forward) whose responsibility would be to forward raw requests from the Relay Server to the service ID (more precisely, service node or data node).
Issue
Type of change
Select one or more from the following:
consensus-breakinglabel if so. See [Infra] Automatically add theconsensus-breakinglabel #791 for detailsSanity Checklist
assignees,reviewers,labels,project,iterationandmilestonemake docusaurus_startmake go_develop_and_testandmake test_e2edevnet-test-e2elabel to run E2E tests in CI