Commit Graph

6 Commits (633b588b1b53b19171467939f39f1b00b7bdb00c)

Author SHA1 Message Date
Johnny Steenbergen 38606c66e1 feat(endpoint): drop id specific check for secret keys in all endpoints
the original design made the secrets unable to be reused, a bit to opinionated
to be useful eleswhere. This relaxes that requirement so that secrets can be
referenced here.
2019-12-17 17:10:27 -08:00
Johnny Steenbergen 86a359f34b chore(http): refactor http layer to be able to encode/decode influxdb.ID's safely
noticed that I had not used the http server as the entry point for server tests.
This was work to make that happen. Along the way, found a bunch of issues I hadn't
seen before 🤦. There are a number of changes tucked away inside the
other types, that make it possible to encode/decode a type with zero value for
influxdb.ID.
2019-12-13 09:46:01 -08:00
Kelvin Wang aed8035472 fix(notification/endpoint): pagerduty clientURL should be optional 2019-09-11 15:26:50 -04:00
Michael Desa ea1b7bec09
fix(pagerduty/rule): change url to clientURL for pagerduty endpoint/rule
Closes https://github.com/influxdata/influxdb/issues/15042

Previously, there was an optional URL provided for the pagerduty
endpoint. However, the pagerduty API url does not change and as a result
it should not have been a parameter. The Pagerduty API does require a
`clientURL` that is presented in the pagerduty UI when an alert is
triggered. Currently that value will default to the alerts history page
for the organization.
2019-09-09 19:09:35 -04:00
Kelvin Wang 23c31c09cb fix(notification/pagerduty): routingKey encode 2019-08-19 12:41:15 -04:00
Kelvin Wang f683f0dc46 feat(notification/endpoint): add endpoint struct
Co-authored-by: Jade McGough <jade@thezets.com>
2019-08-15 21:56:17 -04:00