dpl: Problem deploying to Heroku API V3
I’ve just updated dpl to 1.8.33 and it’s giving this error:
$ dpl --provider=heroku --app=$APP_NAME --api-key=$HEROKU_API_KEY
Installing deploy dependencies
Successfully installed excon-0.55.0
Successfully installed multi_json-1.12.1
Successfully installed heroku-api-0.4.2
3 gems installed
Successfully installed rendezvous-0.1.2
1 gem installed
Preparing deploy
No stash found.
Expected(200) <=> Actual(404 Not Found)
body: "{\"id\":\"not_found\",\"message\":\"The requested API endpoint was not found. Are you using the right HTTP verb (i.e. `GET` vs. `POST`), and did you specify your intended version with the `Accept` header?\"}"
It was working earlier today, then Heroku started to throw some errors telling that the v2 will be shutdown, I thought that the latest updates on the 1.8.33 version would work on the V3 API.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 3
- Comments: 22 (12 by maintainers)
Hi, everyone. I’ve pushed a new code to check API authorization more directly (that is, with
heroku-apigem, but using the correct endpoint). To test it, you’d have to either build it yourself:or deploy it using Travis CI.
https://travis-ci.org/travis-ci/docs-travis-ci-com/builds/237716231#L228 shows a successful deployment using the new method.
I’d appreciate it if you could test it, too.
1.8.35 is out with fixes for the 2 remaining
curlcalls.@cbrzn That is unrelated to this issue.
I’m closing this now, in the absence of clear indications that there is still something amiss.
If you see problems, do open a separate issue with details.
Thanks.
We have released
dpl1.8.34. Heroku API deployment now uses V3 API endpoint exclusively, and supportsrunandrestartcommands as before.I’m going to keep this issue open until the next brownout on Monday, at which time we should know if it really works.
I’m planning on releasing
dpl1.8.34 later today that makes all API calls to the V3 endpoints. We should be ready for the brownout on Monday at 16:00 UTC.