Ported CLI from commander to yargs because yargs suits our large CLI better and is easier to develop with. Split commands into separate files since the file was getting annoyingly long.

lib/cli/notify-slack/index.js

@@ -0,0 +1,54 @@
+module.exports.command = 'notify-slack'
+
+module.exports.describe = 'Start a Slack notifier unit.'
+
+module.exports.builder = function(yargs) {
+  var logger = require('../../util/logger')
+
+  return yargs
+    .env('STF_NOTIFY_SLACK')
+    .strict()
+    .option('channel', {
+      alias: 'c'
+    , describe: 'Slack channel.'
+    , type: 'string'
+    , default: process.env.SLACK_CHANNEL
+    , demand: true
+    })
+    .option('connect-sub', {
+      alias: 's'
+    , describe: 'App-side ZeroMQ PUB endpoint to connect to.'
+    , type: 'array'
+    , demand: true
+    })
+    .option('priority', {
+      alias: 'p'
+    , describe: 'Minimum log level.'
+    , type: 'number'
+    , default: logger.Level.IMPORTANT
+    })
+    .option('token', {
+      alias: 't'
+    , describe: 'Slack API token.'
+    , type: 'string'
+    , default: process.env.SLACK_TOKEN
+    , demand: true
+    })
+    .epilog('Each option can be be overwritten with an environment variable ' +
+      'by converting the option to uppercase, replacing dashes with ' +
+      'underscores and prefixing it with `STF_NOTIFY_SLACK_` (e.g. ' +
+      '`STF_NOTIFY_SLACK_CHANNEL`). Legacy environment variables like ' +
+      'SLACK_TOKEN are still accepted, too, but consider them ' +
+      'deprecated.')
+}
+
+module.exports.handler = function(argv) {
+  return require('../../units/notify/slack')({
+    token: argv.token
+  , channel: argv.channel
+  , priority: argv.priority
+  , endpoints: {
+      sub: argv.connectSub
+    }
+  })
+}