I was playing around with the CLI to see how I can incorporate it into demos and wanted to share a couple of things to remind people of its capabilities.
Note for interactive usage of the CLI, i.e., as a human, you can log in to the platform using your organization’s domain name and password if your organization is delegating authentication to your corporate IdP. Typing the command below will open a browser for you to log in:
As the great Mark Twain once wrote in response to reading his own obituary in May of 1897 , "reports of my death have been greatly exaggerated." Fast forward nearly a hundred years to 1995, and a Finnish computer scientist named Tatu Ylönen created a secure transport protocol known simply as Secure Shell (SSH). What do these things have to do with each other? Nothing, aside from perception.
In its most practical terms, SSH enables users to establish a secure, remote connection with a Linux-based machine via a Command Line Interface (CLI). SSH is the de facto standard for secure server access, and has survived the test of time, despite a significant shift in how infrastructure is operated in the cloud.
Apache Commons CLI, initially released in 2002, is perhaps the most widely-used Java command line parser, but its API shows its age. Applications looking for a modern approach with a minimum of boilerplate code may be interested in Picocli. Why is it worth the trouble to migrate, and how do you migrate your Commons CLI-based application to Picocli? Picocli offers a fluent API with strong typing, usage help with ANSI colors, autocompletion, and a host of other features. Let’s take a look using Checkstyle as an example. (Note: as the author of Picocli, it is fair to say I am biased.)
Is migrating from Commons CLI to Picocli worth the trouble? What is the benefit of moving from one command line parser to another? Is this more than just redecorating the living room of our application?
