The Web UI and messaging channels now read and write Archie's runtime settings through one versioned, audited control-plane API hosted on the State Store's existing gRPC server: catalog, query, command, watch. Each feature owns its resource, validation and commands; storage only writes versions and audit records. Workflows move with it. Definitions become portable YAML compiled through a closed, typed step registry and stored as a control-plane resource, so the yaegi interpretation paths (internal/gate, wfeval, wfextract, gateeval, gateextract, skillbuild) are deleted rather than carried. The UI process reads definitions as data: the JSON projection lives in internal/domain/workflow/task so a dashboard decodes the stored collection without linking the workflow engine, which cmd/archie-ui's deletion gate forbids. Shipped definitions ride the catalog descriptor rather than a bespoke REST route, keeping the API to its four operations. archie-messaging gains -state-store-target/-state-store-token and reads channel settings from the database, failing closed when the State Store is unreachable: the database is authoritative for those settings.
28 lines
745 B
Go
28 lines
745 B
Go
package workflow
|
|
|
|
import (
|
|
"testing"
|
|
"time"
|
|
)
|
|
|
|
func TestExecutionSettingsValidateRejectsNegativeLimits(t *testing.T) {
|
|
t.Parallel()
|
|
|
|
tests := []struct {
|
|
name string
|
|
settings ExecutionSettings
|
|
}{
|
|
{"steps", ExecutionSettings{MaxModelToolSteps: -1, MaxRuntime: time.Second, MaxConsecutiveGateFailures: 1}},
|
|
{"runtime", ExecutionSettings{MaxModelToolSteps: 1, MaxRuntime: -time.Second, MaxConsecutiveGateFailures: 1}},
|
|
{"gate failures", ExecutionSettings{MaxModelToolSteps: 1, MaxRuntime: time.Second, MaxConsecutiveGateFailures: -1}},
|
|
}
|
|
for _, tt := range tests {
|
|
t.Run(tt.name, func(t *testing.T) {
|
|
t.Parallel()
|
|
if err := tt.settings.Validate(); err == nil {
|
|
t.Fatal("Validate() = nil, want error")
|
|
}
|
|
})
|
|
}
|
|
}
|