-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
api: fix duplicate gateway url issue #16464
Conversation
The HashKV should use `/v3/maintenance/hashkv` as url Signed-off-by: Wei Fu <fuweid89@gmail.com>
Will mark it ready after CI green |
This issue not being discovered in the first place means that it is NOT covered by the e2e test cases. We should try to add test case to cover all use cases. Let me take care of it in separate PR. Link to #16454 |
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.
LGTM
Thanks @fuweid
I was using gateway-v2 openapiv2 to find the duplicate issue since the tool returns error. I think the script/genproto.sh can cover it. |
I mean the REST API isn't covered at all in the existing e2e test, otherwise, it should be discovered immediately. |
Yes. 😂 It needs time to add more test cases for it |
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.
Nice work @fuweid. LGTM.
Manually verified that both Will add e2e tests cases in separate PR. |
@fuweid can you please backport this PR to 3.5 as well? thx |
The HashKV should use
/v3/maintenance/hashkv
as urlPlease read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.