hk

I agree! We've been building a CLI that uses an SDK [1] against our new API and so far it's been tremendously helpful in identifying bugs and other problems -- if we hadn't gone through that exercise then we would have inadvertently shipped some of those issues out to our users. I think SDKs are great. The intent of the article was to document why I will sometimes opt out of using them. [1] https://github.com/heroku/hk

Hi everyone, I'm the new maintainer of hk. It's actually not very new :) You can see that Keith Rarick did most of the work on it over a year ago, along with some other major contributors: https://github.com/heroku/hk/graphs/contributors What is new is that I moved it to the Heroku org this week and will be spending a lot of my time turning it into a proper replacement for the Heroku Toolbelt & gem. It's still very early stage software, though. There isn't currently a supported installation method, and it's very far from having all of the necessary features to fully replace the old client. Also, the UX will probably change frequently and things may break, eat your data, etc. So don't rely on it just yet :) That being said, I'm really excited to see where we can take this in the next few months. Hk is already a great starting point. Go is

Are you asking how to do this in Go or how to do it in general? Here's how the hk app does it: https://github.com/heroku/hk/blob/master/main.go#L120 Basically it reads the arguments to the executable and matches them against a built-in list of supported commands and dispatches appropriately.

Yes: https://github.com/heroku/hk/blob/master/about.go