distribution/cmd
Stephen J Day 0a29b59e14 Webhook notification support in registry webapp
Endpoints are now created at applications startup time, using notification
configuration. The instances are then added to a Broadcaster instance, which
becomes the main event sink for the application. At request time, an event
bridge is configured to listen to repository method calls. The actor and source
of the eventBridge are created from the requeest context and application,
respectively. The result is notifications are dispatched with calls to the
context's Repository instance and are queued to each endpoint via the
broadcaster.

This commit also adds the concept of a RequestID and App.InstanceID. The
request id uniquely identifies each request and the InstanceID uniquely
identifies a run of the registry. These identifiers can be used in the future
to correlate log messages with generated events to support rich debugging.

The fields of the app were slightly reorganized for clarity and a few horrid
util functions have been removed.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-02-03 13:32:37 -08:00
..
registry Webhook notification support in registry webapp 2015-02-03 13:32:37 -08:00
registry-api-descriptor-template Move from docker-registry to distribution 2014-12-23 17:13:02 -08:00
registry-storagedriver-azure Move from docker-registry to distribution 2014-12-23 17:13:02 -08:00
registry-storagedriver-filesystem Move from docker-registry to distribution 2014-12-23 17:13:02 -08:00
registry-storagedriver-inmemory Move from docker-registry to distribution 2014-12-23 17:13:02 -08:00
registry-storagedriver-s3 Move from docker-registry to distribution 2014-12-23 17:13:02 -08:00