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.
35 lines
1.2 KiB
Go
35 lines
1.2 KiB
Go
//go:build ignore
|
|
|
|
// log module implementation for archied's EDA playbook engine (Module
|
|
// position, t2db.13). The first action kind: side-effect-free -- it only
|
|
// writes a line to the daemon's log, so it proves the schema -> go:generate
|
|
// -> Yaegi load -> ModuleRegistry -> dispatch mechanism end to end without
|
|
// needing an idempotency answer.
|
|
//
|
|
// Install: copy this file into the configured module_dir (default
|
|
// ~/.config/archie/modules) and restart archied. The daemon evaluates it
|
|
// with Yaegi and registers kind "log". The //go:build ignore tag is a
|
|
// comment to the interpreter, so this file loads normally; the Go toolchain
|
|
// skips it, so it may live inside the module tree.
|
|
//
|
|
// Contract: package main, func Run(log.Args) log.Result -- resolved by name
|
|
// against logextract.Symbols, exactly as a custom gate resolves "gate.Check"
|
|
// against gateextract.Symbols. Args decode is strict: an unknown or
|
|
// wrong-typed field is a reported failure, not a silent zero fill.
|
|
package main
|
|
|
|
import (
|
|
"github.com/samcharles93/archie-core/internal/domain/eda/module/log"
|
|
)
|
|
|
|
func Run(a log.Args) log.Result {
|
|
level := a.Level
|
|
if level == "" {
|
|
level = "info"
|
|
}
|
|
return log.Result{
|
|
Written: a.Message != "",
|
|
Level: level,
|
|
}
|
|
}
|