Messaging service resolves secrets with built-in engines only; plugin engines are never loaded there #1033
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1033
Reference in new issue
Block a user
archied loads plugin secret engines from secret_engine_dir (internal/app/archied/provider_secrets.go: secret.NewRegistry then registry.LoadDir with secretextract, enginehost and yaegi unrestricted symbols). The messaging service builds its own secret.NewRegistry() in internal/app/archiemessaging config.go and run.go and never calls LoadDir, so a Telegram token or webhook signing secret whose reference names a plugin engine (sops, Vault/OpenBao) fails there with 'secret engine not registered' while the same reference resolves in archied. Build every process's registry through one constructor that loads the configured directory, so an engine installed once is available wherever a reference is resolved.
Acceptance criteria
A test resolves a channel secret whose reference names a plugin engine through the messaging service's registry; there is one registry constructor, used by archied and the messaging service.
Notes
The shared constructor already exists: configuredSecretRegistry in internal/app/archied (built-ins + LoadDir(secret_engine_dir) with secretextract, enginehost and yaegi unrestricted symbols), also used by openStateStore for the bindings cipher. Move it below internal/app so archiemessaging can call it in config.go and run.go instead of secret.NewRegistry(). archie-ui stays env-only by design (ui-service-boundary deletion gate). Also correct docs/prds/messaging-service-boundary.md in place: it cites a [secrets] section that does not exist; the setting is top-level secret_engine_dir.
Burndown verified that the old LoadDir architecture is gone. Messaging, gateway and daemon all use secretengine.Supervise over installed packages; State Store intentionally resolves only env because it serves the package registry. The shared supervisor integration test resolves a real extension reference, and the local gateway resolved an installed acceptance engine. The original built-ins-only messaging path is superseded by this implementation.
Close reason
Superseded by shared package-extension supervision in the resolving services.
Imported from beads
archie-core-32jm· GitHub #1053 · type bug · priority P2 · created 2026-09-25 · closed 2026-10-13