Fifth slice of docs/prds/eda-playbook-engine.md (t2db.13), implementing docs/prds/module-position.md's recommended first slice: prove schema -> go:generate -> Yaegi load -> ModuleRegistry end to end with a side-effect-free action kind, before any kind with a real external effect (notify, image-gen, forge writes) -- those stay blocked on the parent doc's unresolved execution-time gaps (idempotency, mid-run failure). - internal/domain/eda/module/log: hand-written schema source (Args/Result/ SchemaVersion per module-position.md) + logextract generated symbol table via go:generate yaegi extract (same tooling as wfextract/ gateextract; scoped to ./internal/domain/eda/module/...). - internal/domain/eda/module: ModuleRegistry with Register(kind, dir) / Invoke(ctx, kind, rawArgs). No generic Module interface with an any payload: each kind is its own tiny package with its own generated contract; the registry's internal storage is the only place erasure appears (exactly as inside wfextract). Invoke decodes rawArgs strictly into the kind's Args before calling the interpreted function -- an unknown key or wrong type is a reported failure, not a silent zero-value fill (the 'schema defines the accepted message' rule). Generalizes gateeval's fixed-signature Yaegi pattern via yaegiutil.New/Resolve/Safe -- no new interpreter-construction or panic-recovery mechanism. - Config: ModuleDir mirroring PluginDir's shape and doc comment (operator-trusted directory of Yaegi module implementations, one .go per kind; empty means none loaded). Wired at daemon startup in bootstrap.go alongside PlaybookDirs loading -- log-and-abort on load failure (a broken module is a startup failure, not degrade-and-skip). - examples/modules/log.go: operator-facing example (//go:build ignore, mirroring examples/secret-engines/) proving the shipped contract. Tests: registry (register/invoke, unknown kind, missing file, strict arg-decode shape failures, malformed file, panic recovery), logextract smoke test, and an example-load test that runs the shipped examples/modules/log.go through the real registry (not a test fixture). task check clean (113/113 UI, exit 0). Playbook YAML action dispatch is deliberately out of this slice: a minimal 'run this one module action, no chaining' dispatch still requires naming how args values reach the action (parent doc open question 1 -- data-flow/interpolation syntax) and what the result feeds, both unresolved by design. Dispatch is a follow-up ticket that consumes this registry as-is; recorded in module-position.md.
33 lines
1.3 KiB
Go
33 lines
1.3 KiB
Go
// Package log is the schema source for the "log" Module action kind -- the
|
|
// side-effect-free proof-of-concept kind for the Module position (t2db.13,
|
|
// docs/prds/module-position.md). A Yaegi module implementing this kind
|
|
// exports a fixed function name against these generated types; the operator's
|
|
// file is the implementation, this package is the contract.
|
|
//
|
|
// This is the hand-written schema. logextract (generated by `go generate`)
|
|
// turns it into the Yaegi symbol table the interpreter uses.
|
|
package log
|
|
|
|
// SchemaVersion is independent of a playbook's own workflow_version, per
|
|
// eda-playbook-engine.md's schema-versioning point.
|
|
const SchemaVersion = 1
|
|
|
|
// Args is the accepted message shape for the log kind. Invoke decodes the
|
|
// playbook's args map into this struct before calling the interpreted
|
|
// function; a shape mismatch is a reported failure, not a silent zero fill.
|
|
type Args struct {
|
|
// Message is the line to write to the daemon's log. Required.
|
|
Message string
|
|
// Level is optional; the implementation may default it.
|
|
Level string
|
|
}
|
|
|
|
// Result is what the log kind returns. It is surfaced as map[string]any so a
|
|
// later data-flow mechanism can use it (module-position.md open question 3).
|
|
type Result struct {
|
|
// Written reports whether the implementation wrote the line.
|
|
Written bool
|
|
// Level echoes the level actually used.
|
|
Level string
|
|
}
|