[RATIS-2113] Use consistent method names and parameter types in RaftUtils

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.1, 3.2.0
• Component/s: shell
• Assignee: Tsz-wo Sze
• Reporter: Tsz-wo Sze
• Created: 14/Jun/24 14:21
• Updated: 10/Sep/24 21:54
• Resolved: 22/Aug/24 16:44

Description

Since RaftUtils is going to be a public API, we should:

• Use consistent method names: getPeerId vs buildRaftPeersFromStr.
• Use consistent parameter types: PrintStream vs Consumer<String>
• Remove duplicated AbstractCommand.parseInetSocketAddress

Issue Links

• is related to: RATIS-2058 Define ratis-common-api
• is related to: RATIS-2095 Move common logic of ratis-shell to RaftUtils so that Ozone shell could share and use common logic
• links to: GitHub Pull Request #1135