skalenetwork / skalenetwork/node-cli
Incorrect сommand Name in fair ssl CLI output
Open
@badrogger is already working on this.
Since Jul 18, 2025.
- Dominant language
- Python
- Stars
- 21
- Forks
- 7
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 5
Description
Describe the bug
The output messages for the fair ssl status and fair ssl upload commands provide incorrect follow-up command suggestions. They refer to the old command name skale instead of the current fair.
Version
CLI version: 3.0.0-fair.1
To Reproduce
Steps to reproduce the behavior:
- Run fair ssl status on FAIR node without any SSL certificates. See that the output suggests using skale ssl upload.
- Run fair ssl upload to successfully upload a certificate. See that the confirmation message suggests using skale ssl status.
Expected behavior
The command outputs should correctly reference fair instead of skale.
Additional context
root@Regression-node-2:~# fair ssl status
No SSL certificates on the node.
Run < skale ssl upload > to add new certificates.
root@Regression-node-2:~# fair ssl upload -c /etc/letsencrypt/archive/regression-register-node2.skalenodes.com/fullchain1.pem -k /etc/letsencrypt/archive/regression-register-node2.skalenodes.com/privkey1.pem
Certificates are successfully uploaded.
You can check status by running < skale ssl status >
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.