Extend the secret-engine contract/registry with an explicit write or update operation for engines that support accepting a value remotely. Preserve the existing resolve-only behaviour for engines that cannot write.
Implement capability discovery, reference validation, engine-specific error mapping, and safe handling of external engine credentials. Do not make a generic remote write path that can silently overwrite arbitrary references.
Coordinate with #433 and the existing engine work (#430-#432); link dependencies in the implementation PR rather than duplicating them.
Acceptance criteria
Engines explicitly declare remote-write support and the allowed operation(s).
Target references are validated and scoped before any value is sent.
Unsupported, unauthorized, invalid-reference, conflict, timeout, and backend-unavailable errors are distinguishable to the caller but never disclose secret material.
Existing resolve calls and non-writing engines remain compatible.
Tests use fakes/httptest and prove the raw value is sent only to the selected engine over the intended boundary.
Close reason
Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.
Imported from beads archie-core-1786748942391-12-7988cdca · GitHub #506 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18
## Scope
Extend the secret-engine contract/registry with an explicit write or update operation for engines that support accepting a value remotely. Preserve the existing resolve-only behaviour for engines that cannot write.
Implement capability discovery, reference validation, engine-specific error mapping, and safe handling of external engine credentials. Do not make a generic remote write path that can silently overwrite arbitrary references.
Coordinate with #433 and the existing engine work (#430-#432); link dependencies in the implementation PR rather than duplicating them.
## Acceptance criteria
- Engines explicitly declare remote-write support and the allowed operation(s).
- Target references are validated and scoped before any value is sent.
- Unsupported, unauthorized, invalid-reference, conflict, timeout, and backend-unavailable errors are distinguishable to the caller but never disclose secret material.
- Existing resolve calls and non-writing engines remain compatible.
- Tests use fakes/httptest and prove the raw value is sent only to the selected engine over the intended boundary.
### Close reason
Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.
---
_Imported from beads `archie-core-1786748942391-12-7988cdca` · GitHub #506 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18_
sam
added the hightask labels 2026-10-27 13:38:29 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Scope
Extend the secret-engine contract/registry with an explicit write or update operation for engines that support accepting a value remotely. Preserve the existing resolve-only behaviour for engines that cannot write.
Implement capability discovery, reference validation, engine-specific error mapping, and safe handling of external engine credentials. Do not make a generic remote write path that can silently overwrite arbitrary references.
Coordinate with #433 and the existing engine work (#430-#432); link dependencies in the implementation PR rather than duplicating them.
Acceptance criteria
Close reason
Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.
Imported from beads
archie-core-1786748942391-12-7988cdca· GitHub #506 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18