Bug 1014296 - Event notification lacks clear documentation of return data
Summary: Event notification lacks clear documentation of return data
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: async/tasks
Version: Master
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-01 16:45 UTC by Eric Helms
Modified: 2014-11-12 13:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-12 13:06:27 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Eric Helms 2013-10-01 16:45:02 UTC 
Description of problem:
Looking through the Pulp documentation on event listeners, I am unable to find clear documentation on what a particular event will return data structure wise.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Clear documentation on what an event notification returns to the user.

Additional info:
Comment 1 Sayli Karmarkar 2013-10-02 15:47:05 UTC 
Eric,

Here are the links to the docs.

https://pulp-dev-guide.readthedocs.org/en/pulp-2.2/integration/events/repo-action-events.html

https://pulp-dev-guide.readthedocs.org/en/pulp-2.2/integration/events/index.html

Can you give some more information about what exactly are you looking for?
Note You need to log in before you can comment on or make changes to this bug.