node info uses --ip instead of --rpc-url, inconsistent with other commands

Open Beginner friendly
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
cli

Research direction

Start at the node info command and compare its flag parsing with the global --rpc-url handling used by wallet, transfer, and subnet. Verify that --rpc-url works for node info, --ip remains compatible, and an IP-only value uses port 9650.

Written by the indexing model from the issue text.

Description

Problem

Every command uses --rpc-url for specifying a custom endpoint, but node info uses --ip:

platform node info --ip 127.0.0.1          # works
platform node info --rpc-url http://127.0.0.1:9650  # ignored, still requires --ip

This is confusing because --rpc-url is a global flag that works everywhere else (wallet, transfer, subnet, etc).

Suggested Fix

  • Accept --rpc-url as the primary way to specify the node (extract host from URL)
  • Keep --ip as an alias for backward compatibility
  • Default port to 9650 when only an IP is provided

Environment

  • platform-cli v1.0.1
Dominant language
Go
Stars
1
Forks
5
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ava-labs/platform-cli

All issues in ava-labs/platform-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.