happyDomain/checker-sdk-go
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

checker: pass EnabledRules to Collect via context

Browse source 
Providers can now skip optional work (network calls, paid API hits) for
rules the host has disabled. The /collect request grows an EnabledRules
field, and server.handleCollect attaches it to the context with
WithEnabledRules; providers read it via EnabledRulesFromContext or the
per-rule RuleEnabled helper.
This commit is contained in:
nemunaire 2026-05-19 22:05:07 +08:00
commit c72558e266
3 changed files with 64 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

13
checker/types.go
View file

@ -421,10 +421,17 @@ type OptionsValidator interface {
}
// ExternalCollectRequest is sent to POST /collect on a remote checker endpoint.
//
// EnabledRules lets the host inform the provider which rules will be evaluated
// downstream, so the provider can skip optional work (network calls, paid API
// hits, …) for data that would not surface in any state. nil means "run
// everything"; an explicit map with a rule name set to false means that rule
// is off. Providers access the value via EnabledRulesFromContext(ctx).
type ExternalCollectRequest struct {
Key ObservationKey `json:"key"`
Target CheckTarget `json:"target"`
Options CheckerOptions `json:"options"`
Key ObservationKey `json:"key"`
Target CheckTarget `json:"target"`
Options CheckerOptions `json:"options"`
EnabledRules map[string]bool `json:"enabledRules,omitempty"`
}
// ExternalCollectResponse is returned by POST /collect on a remote checker endpoint.