Caleb Hailey
Caleb Hailey
## Feature Suggestion The POST APIs (e.g. CheckConfig POST) already return HTTP response code 201 Created and 409 Conflict for when the resource already exists. Extending the PUT APIs to...
## Feature Suggestion Remove the CheckConfig.Spec.Handlers field in favor of the new CheckConfig.Spec.Pipelines field. ## Possible Implementation Version bump the CheckConfig resource to core/v3.CheckConfig. We could potentially offer some backwards...
This is a meta issue, aggregating all outstanding issues & PRs related to filtering of Uchiwa list views by various attributes for discussion and eventual implementation. If you are aware...
Hi there :wave: long time fan of DuckDuckGo here & glad such an alternative to `` exists. My company uses Hubspot and recently started embedding various Hubspot forms & CTA...
Changes: * [ ] Remove support for `type:set` Handlers * [ ] Add Pipelines list/detail views to web-UI * [ ] TBD database migration for converting `type:set` handlers to Pipelines?...
We should only use CheckConfig.Spec.pipelines moving forward; if a pipeline should only process metrics, it can use the built-in `has_metrics` filter.
Add support for new `resource_labels` attribute (using "labels" as selectors), similar to how `resource_names` works, but offering a more dynamic mechanism for granting access to some subset of resources. https://github.com/sensu/sensu-go/blob/0eca3eff1d9621e1cde4c71901875a4a8922cc48/api/core/v2/rbac.proto#L28-L30
## Feature Suggestion One of my favorite features in Sensu Go is the new `sensuctl` CLI utility. It's a natural fit alongside the other modern ops tools in my workflow...
**Is your feature request related to a problem? Please describe.** I'm developing an HTTP API using Vapor where some endpoints may offer support for URL query parameters that have a...