Bug 1014296

Summary:	Event notification lacks clear documentation of return data
Product:	[Retired] Pulp	Reporter:	Eric Helms <ehelms>
Component:	async/tasks	Assignee:	pulp-bugs
Status:	CLOSED CURRENTRELEASE	QA Contact:	pulp-qe-list
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	Master	CC:	ehelms, skarmark
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-12 13:06:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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?