Backport of [NET-3865] [Supportability] Additional Information in the output of 'consul operator raft list-peers' into release/1.14.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #17582 to be assessed for backporting due to the inclusion of the label backport/1.14.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@absolutelightning
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Description

As per requirement of NET - 3865, We want to have the 'commit_index' to be included in the output of 'consul operator raft list-peers -detailed'. This feature specifically useful in the cases where Consul is being upgraded to determine the replication rate and intervene as needed.

I have implemented it by calling a API /v1/operator/autopilot/health, storing the response in a map -> [server id, OperatorHealthReply]. Then this data is used to print the Commit Index by matching the id of server from this to server id in RaftGetConfiguration.

Testing

Create a consul cluster by following this tutorial.
kubectl exec -it consul-server-0 -n consul -- /bin/sh in one terminal
kubectl exec -it consul-server-1 -n consul -- /bin/sh in other terminal
do a ps and kill consul agent in the second terminal.
Run command consul operator raft list-peers

• execute the following command when agent is running
• consul operator raft list-peers
• Output -

PR Checklist

• updated test coverage
• external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• 2f94024 - 7626d09 - 79aabc9 - 44eee41 - 1390353 - d118518 - d46a074 - 539dbc7 - 604b616 - 3a63b3d - 008946c - 509062e - cf22ea5 - eb69358 - 5c2a587 - 8e1f728 - 360ab9e - dc25344 - c461f59 - 3631708 - 5d479e8 - 40dc1e1 - e7afa34 - 8c1bab4 - 6b76d59 - c001e59 - 64e3b0a - 7f8d9d8 - fdad3bb - 1adcb15

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

1 out of 2 committers have signed the CLA.

• absolutelightning
• temp

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR

[absolutelightning]

@david-yu Who will approve from hashicorp/consul-docs?

[absolutelightning]

@analogue Hi, I am not able to merge this. Please help. I have already signed the agreement.
cc @david-yu

[analogue]

@analogue Hi, I am not able to merge this. Please help. I have already signed the agreement. cc @david-yu

@jmurret Any guidance here regarding the "temp" user and the CLA? Is this something we're responsible for or part of a rel-eng owned process?

[jmurret]

@analogue I'm not sure. I'll ping releng and copy you.

[jmurret]

@analogue @absolutelightning

It looks like the PR description when this was created has the answer:

This person should manually cherry-pick the original PR into a new backport PR, and close this one when the manual backport PR is merged in.

There is no way to get around the no-op commit that created this PR. If you don't want to create a new PR, then you can locally do something like the below that will effectively get rid of the no-op commit if you have already cherry-picked into this branch:

git reset --soft release/1.14.x

git commit -m '<insert message about manual cherry pick>'

git push -f

[absolutelightning]

Closing this one have created a new one. #17736
@analogue

[analogue]

Closing this one have created a new one. #17736 @analogue

That is a link back to this PR and I couldn't find a new PR with the same content.

[absolutelightning]

Closing this one have created a new one. #17736 @analogue

That is a link back to this PR and I couldn't find a new PR with the same content.

Here - #17828