Secret engines: list the available engines, pick one in every secret reference, and show them under Settings #356

Closed
opened 2026-10-27 13:35:59 +00:00 by sam · 0 comments
Owner

Every secret reference (Telegram token, webhook signing secret, MiniMax key, provider keys) takes its engine as free text today. Only the processes that resolve secrets know which engines exist: internal/secret.Registry holds the built-ins (env, bws) plus any plugin loaded from secret_engine_dir via LoadDir, and it has no way to list them. archie-ui is a separate process and never loads the plugins.
Needed:

  1. secret.Registry gains a listing (name, version, built-in or plugin).
  2. The resolving process publishes that list where archie-ui can read it. Follow the precedent of the config snapshot and apply-status reports (published by the process, read by the UI process), not a new cross-process call per request.
  3. GET endpoint in internal/webui serving it.
  4. The SecretRefField engine input becomes a select of the published engines. An engine a stored reference names but no process has published stays selectable and is flagged 'not installed'.
  5. Settings > Integrations > Secret engines lists each engine with its version and source, next to Plugins (secret_engine_dir moves there from the plugin-settings page).
    Also offer a resolve check (does this ref resolve?) without ever returning the value.

Acceptance criteria

Picking an engine never involves typing its name; a plugin engine installed on the resolving host appears without an archie-ui restart after the next publish; no secret value crosses to the UI.

Notes

Burndown reconciled the original directory-plugin plan with the current extension architecture. Only env is built in; installed package engines run through secretengine.Supervise in daemon, gateway and messaging. Engine inventory is published in the existing config snapshot, refreshes on supervisor changes, and is read by the UI. The value-free reference check uses the gateway gRPC contract and reports only gateway resolution. The State Store intentionally stays env-only because it serves installed package data. No secret_engine_dir setting exists to move.
Burndown verification: installed a local test engine through the real package API, accepted and enabled it, and observed qa-echo 1.2.3 in the published inventory without a UI reload. Its reference check returned resolved=true with no value. Disabling it removed it from the report; the picker preserved the selected name and key and marked not installed. Existing and missing env references were checked through the real gateway. Shared supervisor integration and HTTP/RPC boundary tests passed.
Before/after screenshots: micl-secret-field-before.png, micl-secret-field-after.png, micl-secret-engines-before.png, micl-secret-engines-after.png. Removed-engine state captured in micl-secret-uninstalled-after.png.

Close reason

Implemented, browser-verified with before/after screenshots and explicit live-versus-fixture evidence; task check passed on commit bbbb5277.


Imported from beads archie-core-micl.21 · GitHub #1062 · type feature · priority P2 · created 2026-09-25 · closed 2026-10-13

Every secret reference (Telegram token, webhook signing secret, MiniMax key, provider keys) takes its engine as free text today. Only the processes that resolve secrets know which engines exist: internal/secret.Registry holds the built-ins (env, bws) plus any plugin loaded from secret_engine_dir via LoadDir, and it has no way to list them. archie-ui is a separate process and never loads the plugins. Needed: 1. secret.Registry gains a listing (name, version, built-in or plugin). 2. The resolving process publishes that list where archie-ui can read it. Follow the precedent of the config snapshot and apply-status reports (published by the process, read by the UI process), not a new cross-process call per request. 3. GET endpoint in internal/webui serving it. 4. The SecretRefField engine input becomes a select of the published engines. An engine a stored reference names but no process has published stays selectable and is flagged 'not installed'. 5. Settings > Integrations > Secret engines lists each engine with its version and source, next to Plugins (secret_engine_dir moves there from the plugin-settings page). Also offer a resolve check (does this ref resolve?) without ever returning the value. ### Acceptance criteria Picking an engine never involves typing its name; a plugin engine installed on the resolving host appears without an archie-ui restart after the next publish; no secret value crosses to the UI. ### Notes Burndown reconciled the original directory-plugin plan with the current extension architecture. Only env is built in; installed package engines run through secretengine.Supervise in daemon, gateway and messaging. Engine inventory is published in the existing config snapshot, refreshes on supervisor changes, and is read by the UI. The value-free reference check uses the gateway gRPC contract and reports only gateway resolution. The State Store intentionally stays env-only because it serves installed package data. No secret_engine_dir setting exists to move. Burndown verification: installed a local test engine through the real package API, accepted and enabled it, and observed qa-echo 1.2.3 in the published inventory without a UI reload. Its reference check returned resolved=true with no value. Disabling it removed it from the report; the picker preserved the selected name and key and marked not installed. Existing and missing env references were checked through the real gateway. Shared supervisor integration and HTTP/RPC boundary tests passed. Before/after screenshots: micl-secret-field-before.png, micl-secret-field-after.png, micl-secret-engines-before.png, micl-secret-engines-after.png. Removed-engine state captured in micl-secret-uninstalled-after.png. ### Close reason Implemented, browser-verified with before/after screenshots and explicit live-versus-fixture evidence; task check passed on commit bbbb5277. --- _Imported from beads `archie-core-micl.21` · GitHub #1062 · type feature · priority P2 · created 2026-09-25 · closed 2026-10-13_
sam added the mediumfeature labels 2026-10-27 13:35:59 +00:00
sam self-assigned this 2026-10-27 13:35:59 +00:00
sam closed this issue 2026-10-27 13:35:59 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#356