create-validator cli command should take in a json file (or validator config file)

[colin-axner]

Summary

Creating a validator via command line can be tricky. There are a lot of required flags you need to specify. I'd propose changing the command so that it takes in a validator.json file that users can modify with their desired fields. That way we can specify defaults but it is easy for the creator to see which fields they can modify. We can provide an initial validator.json with missing required fields to ensure they modify the file.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[anilcse]

+1
I wonder why we have many flags required for create-validator cmd but not for gentx command. @alexanderbez is this just overlooked or is there any reason?

[alexanderbez]

I think this is just poor UX design. So many required flags is an indication of poor design choice in this command. I think having a single arg validator.json is a much better UX as you've suggested 👍

[anilcse]

I think we can make moniker, amount flags as required and keep other flags as optional (same as gentx command). Also, we can have a flag to read from file may be? imho, creating a file is bit odd-experience for users.

[alexanderbez]

The thing is, having a bunch of required flags is an indicator that they should be args, and if you have a bunch of args the UX for that command becomes pretty ugly now.