Wire secret engines into provider discovery and execution #924

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

Production creates only the env registry, never loads secret-engine plugins, and Provider lacks the documented api_key SecretRef. Implement startup plugin loading, backwards-compatible provider secret references, resolved provider discovery/runtime/container propagation, tests, release, and Carina deployment.

Acceptance Criteria

Provider api_key SecretRefs resolve through loaded engines at startup; existing api_key_env remains compatible; discovered providers, chat runtime, taskrun and containers receive resolved credentials without logging or serializing secret values; production composition tests and task check pass.


Imported from beads archie-core-1786637500175-396-fef56da4 · GitHub #417 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08

Production creates only the env registry, never loads secret-engine plugins, and Provider lacks the documented api_key SecretRef. Implement startup plugin loading, backwards-compatible provider secret references, resolved provider discovery/runtime/container propagation, tests, release, and Carina deployment. ### Acceptance Criteria Provider api_key SecretRefs resolve through loaded engines at startup; existing api_key_env remains compatible; discovered providers, chat runtime, taskrun and containers receive resolved credentials without logging or serializing secret values; production composition tests and task check pass. --- _Imported from beads `archie-core-1786637500175-396-fef56da4` · GitHub #417 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumbug labels 2026-10-27 13:38:18 +00:00
sam self-assigned this 2026-10-27 13:38:18 +00:00
sam closed this issue 2026-10-27 13:38:18 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#924