Add support for user-configurable policies which can be used as a series of tests to enforce Sensu configuration policies (e.g. api/v2.Silenced.Spec.Expire > 0).
There are probably a dozen or more sensu/sensu-go issues that we might not implement in the core project that could be implemented as a "monitoring as code" solution via SensuFlow.
The real question is, do we want to build this into SensuFlow directly, or support some concept of "plugins"? 🤔
Add support for user-configurable policies which can be used as a series of tests to enforce Sensu configuration policies (e.g.
api/v2.Silenced.Spec.Expire > 0
).There are probably a dozen or more sensu/sensu-go issues that we might not implement in the core project that could be implemented as a "monitoring as code" solution via SensuFlow.
The real question is, do we want to build this into SensuFlow directly, or support some concept of "plugins"? 🤔