CLI command wishlist

[bedeho]

Whenever you feel like there is something youd like to do over the CLI, just add here. We triage in separate project later.

[kek-mex]

These are the ones which ones came to my mind. I will be adding more of these when they come to my mind.

• I have not found an option/command for joystream-node to list a list of connected peers. A command like this would be great.
• Maybe some kind of a "status" command should exist, which shows the amount of disk space used by joystream-node, and a summary of bandwidth used by it.
• Some kind of a simple block explorer to be used via CLI. This could be a bit tricky to actually develop, but I don't have any idea of how challenging it would actually be.
• List free balance of an address with one command, and it's transactions/transaction count.
• Maybe some command line "chain state" commands such as, check memo, and checking details of an entity with "entityById(EntityId): Entity" I am not sure how relevant how this is though.
• Some kind of a CLI Telemetry
• Ability to send transactions with the CLI tool.

[traumschule]

I was not aware of this issue. Some weeks ago i asked the WG leads what they suggest:

CWG

The first thing to adjust is when the Curator Lead makes processing-applications so that when asked "Do you want to provide an optional RewardPolicy", the default is "Yes". And decode the line: "specify the value for u32:" as "set u32 (payment period, number of blocks)"

SWG

Just a few ideas that quickly come to my mind

• Update manual with more examples. Sometime that's not easy to understand how to work with commands
• Feature that will automatically adjust salaries based on the provided KPIs values

In an ideal world OKRs are measured automatically, then this data (json) is loaded by the CLI to adjust salaries accordingly. I don't really think that SP Lead should do all these steps manually

OWG

• A while back a tried to export an opening but the format was invalid JSON and i was not able to import my own. That would be very helpful also for the coming OG (scenario: web interface with form to create a form - on Submit data is sent to backend/API which executes cli to create the opening with a pre-selected role key)

• Stay connected and show a menu with commands (similar to name selection when you fill an opening)

• Automatically show applications page for (all/active - switch with keystroke) openings on overview page and allow begin review for selected opening

• Applications do not necessarily need to be displayed as JSON, an unordered list is fine too

• Clone existing (closed) opening to hire more workers OR export JSON from a previous opening

[traumschule]

I noticed another issue when hiring: It asks the block for the next payment. Would be handy to have an option In 10 Blocks or Current Block like when creating an opening.

[traumschule]

good first issue:

• accept -k for --backupFilePath: joystream/cli/bin/run account:import -k some_key.json
• adjust amount per argument: working-groups:updateWorkerReward 10 -a 100000
• be more gracious when selecting a group: cli working-groups:updateWorkerReward 2 -g distribution

› Error: Expected --group=distribution to be one of: storageProviders, curators, operationsAlpha, operationsBeta, operationsGamma, gateway, distributors
Accept: alpha, beta, gamma, curation, distribution, storage, or even dwg cwg swg bwg mwg bwg hrwg ..

• show a link to the pioneer block query for every performed transaction: /#/explorer/query/<blockheight> or log the block
• for distributor/storage CLI: operator:set-metadata warn if endpoint returns no valid status / status code !== 200