{"action":"created","issue":{"url":"https://api.github.com/repos/xchapter7x/autopilot/issues/2","labels_url":"https://api.github.com/repos/xchapter7x/autopilot/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/xchapter7x/autopilot/issues/2/comments","events_url":"https://api.github.com/repos/xchapter7x/autopilot/issues/2/events","html_url":"https://github.com/xchapter7x/autopilot/pull/2","id":113657015,"number":2,"title":"Adds usage message when push-zdd is ran without arguments","user":{"login":"trayo","id":6809782,"avatar_url":"https://avatars.githubusercontent.com/u/6809782?v=3","gravatar_id":"","url":"https://api.github.com/users/trayo","html_url":"https://github.com/trayo","followers_url":"https://api.github.com/users/trayo/followers","following_url":"https://api.github.com/users/trayo/following{/other_user}","gists_url":"https://api.github.com/users/trayo/gists{/gist_id}","starred_url":"https://api.github.com/users/trayo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trayo/subscriptions","organizations_url":"https://api.github.com/users/trayo/orgs","repos_url":"https://api.github.com/users/trayo/repos","events_url":"https://api.github.com/users/trayo/events{/privacy}","received_events_url":"https://api.github.com/users/trayo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-10-27T18:58:50Z","updated_at":"2015-10-27T22:10:40Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/xchapter7x/autopilot/pulls/2","html_url":"https://github.com/xchapter7x/autopilot/pull/2","diff_url":"https://github.com/xchapter7x/autopilot/pull/2.diff","patch_url":"https://github.com/xchapter7x/autopilot/pull/2.patch"},"body":"We noticed when you try to run `cf push-zdd` there is no feedback from the command.\r\n\r\nNow when you run the `push-zdd` command, it prints usage:\r\n```\r\n$ cf push-zdd\r\nUSAGE:\r\n   Push a single app (with or without a manifest):\r\n   cf push APP_NAME [-b BUILDPACK_NAME] [-c COMMAND] [-d DOMAIN] [-f MANIFEST_PATH]\r\n   [-i NUM_INSTANCES] [-k DISK] [-m MEMORY] [-n HOST] [-p PATH] [-s STACK] [-t TIMEOUT]\r\n   [--no-hostname] [--no-manifest] [--no-route] [--no-start]\r\n```\r\n\r\ncc: @jordanicollier"},"comment":{"url":"https://api.github.com/repos/xchapter7x/autopilot/issues/comments/151660316","html_url":"https://github.com/xchapter7x/autopilot/pull/2#issuecomment-151660316","issue_url":"https://api.github.com/repos/xchapter7x/autopilot/issues/2","id":151660316,"user":{"login":"xchapter7x","id":690387,"avatar_url":"https://avatars.githubusercontent.com/u/690387?v=3","gravatar_id":"","url":"https://api.github.com/users/xchapter7x","html_url":"https://github.com/xchapter7x","followers_url":"https://api.github.com/users/xchapter7x/followers","following_url":"https://api.github.com/users/xchapter7x/following{/other_user}","gists_url":"https://api.github.com/users/xchapter7x/gists{/gist_id}","starred_url":"https://api.github.com/users/xchapter7x/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xchapter7x/subscriptions","organizations_url":"https://api.github.com/users/xchapter7x/orgs","repos_url":"https://api.github.com/users/xchapter7x/repos","events_url":"https://api.github.com/users/xchapter7x/events{/privacy}","received_events_url":"https://api.github.com/users/xchapter7x/received_events","type":"User","site_admin":false},"created_at":"2015-10-27T22:10:40Z","updated_at":"2015-10-27T22:10:40Z","body":"changes are failing in wercker for this PR. Ill make the wercker app public so you can view the output.\r\n\r\nwe use wercker a lot. When run locally it will spin up docker containers and run everything in the exact same container as it will eventually run in the wercker service. So it is really consistent and reliable. executing ./testrunner is simply a convenience wrapper to running the wercker cli and testing the repo.\r\n\r\n\r\nAlso, in regards to the specific failures, those suits are required to run the tests, as we are using ginkgo and gomega which is a BDD testing framework. Also, we are using godeps to vendor up dependencies which would require you to run `godep go test ./...` rather than `go test ./...`\r\n\r\nIn regards to the error you pasted above, it looks like your network is man in the middle hijacking your certs. Reason i say this is b/c s3.amazonaws.com def has a valid cert, but the error says it doesnt.\r\n\r\nonce you get the build green I'd be happy to accept a pull request for a feature enhancement."}}