I took a slightly unfortunate implementation path. Since most of the CLI is concerned with building commands from configuration, there is no real execution time context available outside of the command-line itself so I cheated a little by storing the API key on the sparkpost instance using (hopefully) unique field name _cliAPIKey. That leaves it accessible for the commands to check later on.
avigoldman
commented
7 years ago
I took a slightly unfortunate implementation path. Since most of the CLI is concerned with building commands from configuration, there is no real execution time context available outside of the command-line itself so I cheated a little by storing the API key on the sparkpost instance using (hopefully) unique field name
_cliAPIKey. That leaves it accessible for the commands to check later on.