Yahcli Rewrite: Motivation and Brainstorming

This ticket is an exploration ticket for rewriting yahcli, one of the tools that devops uses to manage the network. We want to identify and enumerate yahcli's current pros and cons, as well as the pros and cons of a potential rewrite. Some of this analysis will come from yahcli's code; additionally, it's important to collect and assemble relevant details from the tool's contextual past.
Historically the burden of maintenance has fallen on @tinker-michaelj, so he's a critical source to consult with. As yahcli's primary user, devops will be most familiar with its pain points.

After exploring our motivations for rewriting the tool, brainstorm some ideas for a new version of yahcli. Some interesting questions to answer might include:
* What technologies would it use?
* Who would maintain the project? Who would curate its
* How would a new solution solve yahcli's current pain points?