etcdctl: fix json output

[kstrifonoff]

Fix #19262

[k8s-ci-robot]

Hi @kstrifonoff. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kstrifonoff]

/cc @ivanvc

[ivanvc]

Hi @kstrifonoff, thanks for the pull request. I'm respectful to the original contributor who asked to work on this. Our guideline is to re-assign after a week of no answer when asking a contributor for updates.

A couple of suggestions by quickly looking at the code.

1. The imports contain a lint error. Running make verify-lint locally will show you the error.
2. The code doesn't have unit tests for this, but there's an e2e test, TestCtlV3MemberListWithHex. I think the test should pass, but adding your new cases would be good.
3. I suggest reviewing the code from printKV. I think it would be better to follow that implementation approach, i.e., there would be less repetition with the if conditions.

Thanks again for your pull request :)

[kstrifonoff]

Hi @ivanvc ,

I’ve made some changes to my initial suggestions based on your feedback.

Now, the “JSON with Hex” implementation is just a slight extension of the default “printJSON” implementation. I think it should probably be moved into the “utils” package.

Here are a few things I noticed:

1. The implementation assumes marshalling back and forth the default JSON string, which can be inefficient, but I assume it’s still okay for the CLI.
2. Also, the current approach makes it easy to add “json with hex” output for all the rest of commands that support JSON output.
3. I’m not sure what kind of end-to-end test should be done here. What should it cover? It’s also not clear to me what the current end-to-end test actually checks.

[ivanvc]

/ok-to-test

[ivanvc]

I’m not sure what kind of end-to-end test should be done here. What should it cover? It’s also not clear to me what the current end-to-end test actually checks.

The e2e tests already exist, my suggestion is to expand them to cover the new cases you added:

etcd/tests/e2e/ctl_v3_member_test.go

Lines 206 to 255 in 9f1709e

	func memberListWithHexTest(cx ctlCtx) {
	resp, err := getMemberList(cx, false)
	if err != nil {
	cx.t.Fatalf("getMemberList error (%v)", err)
	}
	cmdArgs := append(cx.PrefixArgs(), "--write-out", "json", "--hex", "member", "list")
	proc, err := e2e.SpawnCmd(cmdArgs, cx.envMap)
	if err != nil {
	cx.t.Fatalf("memberListWithHexTest error (%v)", err)
	}
	var txt string
	txt, err = proc.Expect("members")
	if err != nil {
	cx.t.Fatalf("memberListWithHexTest error (%v)", err)
	}
	if err = proc.Close(); err != nil {
	cx.t.Fatalf("memberListWithHexTest error (%v)", err)
	}
	hexResp := etcdserverpb.MemberListResponse{}
	dec := json.NewDecoder(strings.NewReader(txt))
	if err := dec.Decode(&hexResp); errors.Is(err, io.EOF) {
	cx.t.Fatalf("memberListWithHexTest error (%v)", err)
	}
	num := len(resp.Members)
	hexNum := len(hexResp.Members)
	if num != hexNum {
	cx.t.Fatalf("member number,expected %d,got %d", num, hexNum)
	}
	if num == 0 {
	cx.t.Fatal("member number is 0")
	}
	if resp.Header.RaftTerm != hexResp.Header.RaftTerm {
	cx.t.Fatalf("Unexpected raft_term, expected %d, got %d", resp.Header.RaftTerm, hexResp.Header.RaftTerm)
	}
	for i := 0; i < num; i++ {
	if resp.Members[i].Name != hexResp.Members[i].Name {
	cx.t.Fatalf("Unexpected member name,expected %v, got %v", resp.Members[i].Name, hexResp.Members[i].Name)
	}
	if !reflect.DeepEqual(resp.Members[i].PeerURLs, hexResp.Members[i].PeerURLs) {
	cx.t.Fatalf("Unexpected member peerURLs, expected %v, got %v", resp.Members[i].PeerURLs, hexResp.Members[i].PeerURLs)
	}
	if !reflect.DeepEqual(resp.Members[i].ClientURLs, hexResp.Members[i].ClientURLs) {
	cx.t.Fatalf("Unexpected member clientURLs, expected %v, got %v", resp.Members[i].ClientURLs, hexResp.Members[i].ClientURLs)
	}
	}
	}

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 135 lines in your changes missing coverage. Please review.

Project coverage is 68.66%. Comparing base (37eaafa) to head (13c7989).

Files with missing lines	Patch %	Lines
etcdctl/ctlv3/command/printer_json.go	0.00%	135 Missing ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
etcdctl/ctlv3/command/printer_json.go	0.00% <0.00%> (ø)

... and 22 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #19469      +/-   ##
==========================================
- Coverage   68.81%   68.66%   -0.15%     
==========================================
  Files         421      421              
  Lines       35852    35940      +88     
==========================================
+ Hits        24672    24679       +7     
- Misses       9753     9838      +85     
+ Partials     1427     1423       -4     

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 37eaafa...13c7989. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kstrifonoff
Once this PR has been reviewed and has the lgtm label, please assign serathius for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kstrifonoff]

hi @ivanvc
Could you give it another look? I’ve made a few changes since we last spoke. The initial solution had a bug, so I’ve fixed it.

I’ve also fixed all the remaining member and existing endpoint commands. Now, you can also use them with json and hex output.
I’ve also extended the e2e tests as suggested.

Let me know if you have any questions!

[kstrifonoff]

@ivanvc just a friendly reminder: could you please review this once you have some time?