[
https://issues.apache.org/jira/browse/IGNITE-17417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-17417:
------------------------------------
Fix Version/s: 3.0.0-beta2
> Node name support in CLI
> ------------------------
>
> Key: IGNITE-17417
> URL: https://issues.apache.org/jira/browse/IGNITE-17417
> Project: Ignite
> Issue Type: Task
> Components: cli
> Reporter: Aleksandr
> Assignee: Ivan Gagarkin
> Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-beta2
>
> Time Spent: 8h
> Remaining Estimate: 0h
>
> Now there is only one way to point at the ignite node in the CLI – `node-url`
> or `cluster-url` options. They are represented as an URL that sometimes is
> too annoying to type and remember. It would be much more user-friendly to
> have the second option here. I think node name could be used as a CLI option.
> I propose to add `node-name` option to every command that requires
> `cluster-url` or `node-url`. So, the following user story would be possible:
> {code:bash}
> > ignite
> [disconnected]> connect node2
> [node2]> connect node2
> [node2]> node config show --node-name node1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
