Closed portertech closed 7 years ago
I'd love to see @amdprophet tackle this.
@amdprophet using the current Sensu definitions for filters, mutators, and handlers is probably the best way to start. We can tweak/change how they are configured later, when we know more about any constraints imposed by golang, i.e. filter eval attributes.
Should probably wait for https://github.com/sensu/sensu-go/pull/54 to be reviewed and merged, as it includes some of this work.
Going to pair with @amdprophet on this tomorrow \o/
I removed filters from the task list, as we do not yet know what they are going to look like.
This was implemented in PR #67 which has been merged.
This work will lay the foundations for the traditional Sensu pipeline configuration.
See https://github.com/sensu/sensu-go/pull/40 for example implementation.
We may need to refactor
http_api.go
, splitting up/out the endpoints.