3scale/issues-test — Issue #433: webhooks extensions
Author: HakubJozak
Created: 2012-02-10 17:56:11+00:00
State: open
Labels: feature

webhooks extentions due to Kronovia (end of August) (make consistent with pivotal https://www.pivotaltracker.com/story/show/16115457) Those are not webhooks but emails that need to be send. As a rule of thumb a webhook should be matched by the email events. If something triggers and email, it should also be catchable as a webhook.

Tasks
- adding/removing an app_key must fire an event
- admins actions (besides buyers) should also trigger events (also, add setting to enable disable)
- refreshing a user_key must fire an event
- implement a test method (ping button that send ping from 3scale to the url of the webhood)
- make webhooks actually fire on new events
- controllers with no users should fire (i.e. signup controllers)
- account plan change fire webhooks
- make UI for all new events
- try testing to_xml from outside rails to cover strange load issue on resque workers
- check all messages in the app to see which ones make sense as web hooks
- application plan change fire webhooks
- make webhook post an xml as josep explained
- write assembla doc

https://www.pivotaltracker.com/story/show/17177457