registry/storage/notifications
Stephen J Day 080e329cb1 Separate request data from actor in Event
To clarify the role of actor, the request data that initiates an event has been
separated. The ActorRecord is pared down to just the username. This eliminates
confusion about where event related data should be added.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-02-03 13:32:37 -08:00
..
bridge.go Separate request data from actor in Event 2015-02-03 13:32:37 -08:00
endpoint.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00
event.go Separate request data from actor in Event 2015-02-03 13:32:37 -08:00
event_test.go Separate request data from actor in Event 2015-02-03 13:32:37 -08:00
http.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00
http_test.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00
listener.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00
listener_test.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00
metrics.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00
sinks.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00
sinks_test.go Implement notification endpoint webhook dispatch 2015-02-03 13:30:20 -08:00