Stop calling back to candlepin for qpid messages
|Assigned To:||Justin Sherrill|
|Target version:||Team Brad - Iteration 14|
|Velocity based estimate||-|
Description of problem:
Currently candlepin is sending large messages through candlepin and we are taking these messages, pulling out some ID and fetching the data from candlepin. All the data we need is right there. We should just use it directly. This should speed up processing of events considerably.
Fixes #19026 - reduce qpid-based candlepin callbacks
Previously we would callback to candlepin to fetch pool and consumer
information whenever certain qpid messages were recieved.
- Makes complicance.created messages no longer call back to candlepin
at all, instead it uses the data on the message
- Starts using the katello event queue for processing pool updates.
This feature de-duplication, so if 1000, events come in on the same
pool, only a few requests should be made.