ce91d56d51
For publishing new events into an exchange.
PipelineHandlers can return new Events for subsequent processing.
However, sometimes we need to publish Notifications. Remember that
Notifications are less restrictive than Events. They can be larger.
They can be nested. They can contain lists.
We store these pending notifications in the handler env variable
so downstream handlers can access them.
The NotabeneHandler takes a configuration variable 'env_keys' which
specifies the env keys to look for. Lists of notifications in these
variables are published to the queue using the connection parameters
supplied.
Errors in transmission are logged and ignored since exceptions during
the commit() phase do not flag the steam as in error.
A sample pipeline definition might look like this:
test_expire_pipeline:
- logger
- usage
- name: notabene
params:⋅
host: localhost
user: guest
password: guest
port: 5672
vhost: /
library: librabbitmq
exchange: nova
exchange_type: topic
queue_name: monitor.info
env_keys:
- usage_notifications
Change-Id: If1958135ad6fbed88e2c18b9fac7efde51ee3113
12 lines
145 B
Plaintext
12 lines
145 B
Plaintext
simport
|
|
stackdistiller
|
|
timex
|
|
python-daemon
|
|
MySQL-python
|
|
alembic>=0.4.1
|
|
enum34>=1.0
|
|
SQLAlchemy>=0.9.6
|
|
python-dateutil
|
|
requests
|
|
notabene>=0.0.dev0
|