Documentation
¶
Overview ¶
Package probe works out what this machine can offer the dispatcher (supervise.md §factory-agent probe): a HarnessOffer per configured harness, the configured labels, and the base tooling the host itself needs. It never calls the dispatcher.
The harnesses run in the VM, so a harness is offered by its Prober (supervise and probe use the login prober: the owner's model login is in the state dir); Configured reports what the local config says.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type BaseTooling ¶
type BaseTooling struct{ Commands Commands }
BaseTooling checks BaseTools on PATH.
type Configured ¶
type Configured struct{ Name string }
Configured is the default Prober: the offer is the local config's models, efforts and default, with the harness's subscription login assumed (the PoC runs both harnesses on their owners' subscriptions, 10-poc.md). The adapters replace it with real detection.
func (Configured) Probe ¶
func (c Configured) Probe(_ context.Context, h config.Harness) (v1alpha1.HarnessOffer, error)
Probe implements Prober.
type Dropped ¶
type Dropped struct {
Kind string `json:"kind"` // harness
Name string `json:"name"`
Reason string `json:"reason"`
}
Dropped is a configured harness that isn't advertised, and why.
type Options ¶
type Options struct {
// Harnesses maps a harness name to its Prober; a configured harness without one is
// probed with Configured.
Harnesses map[string]Prober
// Tooling checks the base tooling; nil skips the check.
Tooling Tooling
}
Options say how to probe. Nil maps and a nil Tooling use the defaults.
type Prober ¶
type Prober interface {
Probe(ctx context.Context, cfg config.Harness) (v1alpha1.HarnessOffer, error)
}
Prober probes one harness: harness-adapters.md's Adapter.Probe.
type Report ¶
type Report struct {
Capabilities v1alpha1.AgentCapabilities `json:"capabilities"`
Dropped []Dropped `json:"dropped,omitempty"`
Tooling []Tool `json:"tooling,omitempty"`
}
Report is what a probe found.