Background

In the v2.12.0, the mainline CLI was not compatible with the stable server release. Since our default method of installation points to mainline, messaging the correct version to users may be inconsistent. IE, if they have an internal wrapper for the install script but don't consistently use stable for production, the install flag may not be consistent. We should support a method of installing the same binary as your deployment.

Proposal

For users who have already authenticated an outdated CLI, and want to upgrade:

We could take the deployment URL / token to identify the desired version. The user would be prompted upon running the install script to use their deployment's server version by default, or force the server version with a --server flag.

# implicitly detects server version from stored config
... install.sh --server

Or could we support something like the following?

... install.sh --server <deployment_url>

Which takes the server version from the URL, but I suppose this would be awkward for unauthenticated users, or those downloading the CLI for the first time.