nodejitsu/jitsu — Issue #177: [flatiron] `jitsu users confirm` doesn't resolve
Author: jesusabdullah
Created: 2012-02-24 00:45:31+00:00
State: open
Labels: medium-priority, regression

So far, I've found that `jitsu.commands.users.confirm` isn't defined when the cli plugin tries to resolve it. With a few console.errors and a console.trace, here's what I found:

```

% jitsu users confirm
info: Welcome to Nodejitsu
info: It worked if it ends with Nodejitsu ok
info: Executing command users confirm
{ config:
{ usage:
[ '`jitsu config *` commands allow you to edit your',
'local jitsu configuration file. Valid commands are:',
'',
'jitsu config list',
'jitsu config set ',
'jitsu config get ',
'jitsu config delete ' ],
set: { [Function] usage: [Object] },
get: { [Function] usage: [Object] },
delete: { [Function] usage: [Object] },
list: { [Function] usage: [Object] } },
conf: [Getter],
create: [Getter],
deploy: [Getter],
list: [Getter],
users:
{ usage:
[ '`jitsu users *` commands allow you to work with new',
'or existing user accounts',
'',
'jitsu users available ',
'jitsu users changepassword',
'jitsu users create',
'jitsu users forgot ',
'jitsu users login',
'jitsu users logout',
'jitsu users whoami',
'',
'You will be prompted for additional user information',
'as required.' ],
available: { [Function] usage: [Object] },
create: { [Function] usage: [Object] },
login: { [Function] usage: [Object] },
logout: { [Function] usage: [Object] },
forgot: { [Function] usage: [Object] },
changepassword: { [Function] usage: [Object] },
whoami: { [Function] usage: [Object] } },
login: [Getter],
logout: [Getter],
signup: [Getter],
whoami: [Getter] }
Trace: ohoho
at executeCommand (/home/josh/dev/nodejitsu/jitsu/node_modules/flatiron/lib/flatiron/plugins/cli.js:276:17)
at Object. (/home/josh/dev/nodejitsu/jitsu/node_modules/flatiron/lib/flatiron/plugins/cli.js:320:5)
at [object Object].dispatch (/home/josh/dev/nodejitsu/jitsu/node_modules/flatiron/node_modules/director/lib/director/cli.js:50:21)
at execCommand (/home/josh/dev/nodejitsu/jitsu/lib/jitsu.js:183:18)
at [object Object].setup (/home/josh/dev/nodejitsu/jitsu/lib/jitsu.js:217:3)
at [object Object].exec (/home/josh/dev/nodejitsu/jitsu/lib/jitsu.js:196:33)
at /home/josh/dev/nodejitsu/jitsu/lib/jitsu.js:147:20
at onComplete (/home/josh/dev/nodejitsu/jitsu/node_modules/flatiron/node_modules/broadway/lib/broadway/app.js:86:5)
at Object.ensure (/home/josh/dev/nodejitsu/jitsu/node_modules/flatiron/node_modules/broadway/lib/broadway/features/index.js:10:10)
at ensureFeatures (/home/josh/dev/nodejitsu/jitsu/node_modules/flatiron/node_modules/broadway/lib/broadway/app.js:92:18)
help: `jitsu users *` commands allow you to work with new
help: or existing user accounts
help:
help: jitsu users available
help: jitsu users changepassword
help: jitsu users create
help: jitsu users forgot
help: jitsu users login
help: jitsu users logout
help: jitsu users whoami
help:
help: You will be prompted for additional user information
help: as required.
help:
help: Options:
help: --version, -v print jitsu version and exit [string]
help: --localconf search for .jitsuconf file in ./ and then parent directories [string]
help: --jitsuconf, -j specify file to load configuration from [string]
help: --noanalyze skip require-analyzer: do not attempt to dynamicially detect dependencies [boolean]
help: --colors --no-colors will disable output coloring [boolean] [default: true]
info: Nodejitsu ok
```

This used to work until sometime between last night and this afternoon, and is probably due to a regression in either `flatiron.plugins.cli` or `flatiron-cli-users`.