heroku/kensa — Issue #10: PlanChangeCheck doesn't match add-on API spec for plan change
Author: shayfrendt
Created: 2011-10-16 19:18:52+00:00
State: open

This is albeit a tiny detail, but my implementation was relying on it and was broken as a result:

In the Plan Change section of the add-on [API Specification](https://addons.heroku.com/provider/resources/technical/reference/api-spec), the listed Input JSON is the following:

Action : PUT /heroku/resources/:id
Input : json { "heroku_id": "app123@heroku.com", "plan": "premium" }

However, when running `kensa test planchange 123`, I noticed that the "heroku_id" parameter isn't actually passed:
https://github.com/heroku/kensa/blob/1.1.4/lib/heroku/kensa/check.rb#L356

Should the add-on API spec be updated to match the kensa implementation, or vice-versa?