-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
charon get command #2962
Comments
This is a slippery slope, we risk filling the terminal with lots of information that nobody ends up really using.
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?
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
The text was updated successfully, but these errors were encountered: