influxdb/notification/endpoint
Johnny Steenbergen 300d89887d chore(kv): refactor notification endpoint to use reusable uniqByNameStore
this is work moving us towards more reusable components that add some
rigidity around handling indexes and the entity bucket. The behavior
is very common across much of the kv pkg. This can be reused throughout.
adding some easy wins for tracing(eventually metrics) that enable more
insight that what is currently possible. It normalizes these concerns
across the kv store.
2019-12-30 16:44:57 -08:00
..
endpoint.go chore(kv): refactor notification endpoint to use reusable uniqByNameStore 2019-12-30 16:44:57 -08:00
endpoint_test.go feat(endpoint): drop id specific check for secret keys in all endpoints 2019-12-17 17:10:27 -08:00
http.go feat(endpoint): drop id specific check for secret keys in all endpoints 2019-12-17 17:10:27 -08:00
pagerduty.go feat(endpoint): drop id specific check for secret keys in all endpoints 2019-12-17 17:10:27 -08:00
slack.go feat(endpoint): drop id specific check for secret keys in all endpoints 2019-12-17 17:10:27 -08:00