secret engine plugin: bws (Bitwarden Secrets Manager) #938
Notifications
Due Date
No due date set.
Blocks
Depends on
#939 secret engine plugin: vault/openbao
sam/archie
#937 secret engine plugin: sops
sam/archie
Reference: sam/archie#938
Reference in new issue
Block a user
Ship a yaegi-loaded secrets engine plugin wrapping the bws CLI (os/exec), following the internal/secret Engine interface from archie-core-xec.
Close reason
Already delivered as a compiled-in engine, not a plugin. internal/secret/bws.go implements secret.Engine and shells out to the bws CLI via os/exec (commit
3ae59c9, 2026-07-31); NewRegistry/DefaultRegistry register it under the name "bws" alongside "env". It is documented in config.example.toml and ARCHITECTURE.md:208, and config.example.toml:64 uses it as the worked example. Shipping a second yaegi implementation under examples/secret-engines/ would register the same name "bws", and Registry.Register is last-write-wins over LoadDir, so the plugin would silently shadow the compiled-in engine -- two authoritative paths for one behaviour, which the architecture contract prohibits. Reopen only if the intent is to REPLACE the compiled-in engine with a plugin (which would also need bws removed from NewRegistry and the docs updated).Imported from beads
archie-core-1786637500602-410-7a461d4d· GitHub #431 · type task · priority P2 · created 2026-08-08 · closed 2026-08-20