Open OisinKyne opened 5 months ago
Neat summary of full cluster details? (in a manner that could describe e.g. a 1k key cluster)
This is a slippery slope, we risk filling the terminal with lots of information that nobody ends up really using.
charon get validators
The current iteration of this command supports a flag to print validator addresses in plaintext, to allow for scripting.
WDYT about porting over that functionality?
or stick to the plurals for now
If we make the CLI output easily manageable through shell piping, I would stick with plurals.
🎯 Problem to be solved
We want to return information to the charon node operator about the running cluster in a manner easier than opening the cluster-lock.json. This will become more important as we move to mutable cluster state and have a no longer human readable data file.
We need to develop getters for key lock file information. Ideally, it can be supplemented with access to a CL (and maybe one day an EL) to provide additional information and filtration.
🛠️ Proposed solution
Describe the solution to be implemented
[Wishlist first draft]
Open questions
get operator <id>
or stick to the plurals for now, and only add commands that summarise all operators? same forget validator(s)
🧪 Tests