First-Run Experience

[jbristowe]

The first-run experience of the CLI should be forgiving and provide users with the ability to configure it for subsequent runs.

Currently, the CLI assumes the presence of the following environment variables in order to perform operations against Octopus Deploy:

• OCTOPUS_API_KEY: the API key used to communicate with the Octopus Deploy instance
• OCTOPUS_HOST: the URI of Octopus Deploy instance
• OCTOPUS_SPACE: the ID or name of the space in Octopus Deploy

If these environment variables are missing from the host environment, the CLI should prompt the user for these values. It may be warranted to persist these values to the host's environment. (This is an open question; should we do this?)

[borland]

Currently the CLI will prompt for space but not the other two. It feels like a good idea to persist them; if you have to interactively select the space each time you invoke the CLI, it ends up being quite annoying.

Persisting space and host feels safe and simple. Perhaps we need to be cautious around persistence of an API key for security reasons?

[jbristowe]

It may be worthwhile to look into persisting sensitive values (i.e. OCTOPUS_API_KEY) in secure storage that's provided by the host environment. For example, we could persist this value in keychain.app for macOS or Credential Manager on Windows.