Npm API seems to be broken

I have used the npm API before and it worked.

However, now it seems to be broken. The http request / curl just throws out the standard 'npm --help' output irrespective of the command passed. If I pass an invalid command, then it gives the error with the supported commands.

I used the following smartdocs

http://apigee.com/docs/management/apis/get/organizations/%7Borg_name%7D/apis/%7Bapi_name%7D/revision...

0 5 251
5 REPLIES 5

Not applicable

I'm running into the same error @Prashanth Subrahmanyam . Even when with cURL or SmartDocs. it doesn't seem to execute any command. Any idea what's going on @arghya das or @Greg Brail?

$ curl https://api.enterprise.apigee.com/v1/organizations/testmyapi/apis/nodejs-winston-log-api/revisions/1... -H 'Content-Type:application/x-www-form-urlencoded' -d 'command=install' -u $ae_username:$ae_password


Usage: npm <command>


where <command> is one of:
    add-user, adduser, apihelp, author, bin, bugs, c, cache,
    completion, config, ddp, dedupe, deprecate, docs, edit,
    explore, faq, find, find-dupes, get, help, help-search,
    home, i, info, init, install, isntall, issues, la, link,
    list, ll, ln, login, ls, outdated, owner, pack, prefix,
    prune, publish, r, rb, rebuild, remove, repo, restart, rm,
    root, run-script, s, se, search, set, show, shrinkwrap,
    star, stars, start, stop, submodule, tag, test, tst, un,
    uninstall, unlink, unpublish, unstar, up, update, v,
    version, view, whoami


npm <cmd> -h     quick help on <cmd>
npm -l           display full usage info
npm faq          commonly asked questions
npm help <term>  search for help on <term>
npm help npm     involved overview


Specify configs in the ini-formatted file:
    /home/apigee/.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help confi

adas
Participant V

I see this behaviour in cloud. Opened a regression bug, hoping to get it fixed in the next release. I will investigate and find out what caused the regression.

adas
Participant V

@Prashanth Subrahmanyam and @Diego Zuluaga The npm fix was pushed to our cloud along with the Release_150902. I was waiting for the releases to be rolled out to all regions before putting my comment in community and hence the delay. Please let me know, if you still see this problem.

is this impacting private cloud too?

@Benjamin Goldman I don't think so. We introduced this regression in one of the cloud releases but the recent release has the fix for it. The bug would have never made it to the private cloud releases, so you should be fine.