refactor(services): consume dunite-hibp + dunite-webhook, drop bunyip copies #494
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/DEV-527-consume-hibp-webhook"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Consumes the
dunite-webhook+dunite-hibpleaf crates (dunite #37, DEV-527) and removes bunyip's copies.password_breach.rs-> a re-export shim overdunite_hibp(check_password_breach/is_breached/BreachCheckOutcome). The threeis_breachedcall sites inservices/auth.rsare unchanged.webhook.rs->WebhookServicekeeps its bunyip surface (new/notify_maintenance_change/notify_active_change/notify_account_deleted/dispatch_account_deleted), building each payload from anApplication, but delegates signing + delivery todunite_webhook::WebhookSender. The local sign/send/dispatch impl (and the threesignunit tests, now in dunite) are removed; the Application-payload, retry-exhaust, and no-url tests stay.Pins
Adds
dunite-hibp+dunite-webhookat82f9baaas leaf deps (they own their types, no dunite-core dep), so they pin independently and do NOT move the dunite-core graph rev.reqwest0.11 unifies with the copy bunyip already pulls viadunite-oci/dunite-download.Behaviour
Identical wire shape: event payloads, the
X-Webhook-SignatureHMAC, the 3-attempt exponential backoff, and the no-url no-op. One log change: on a transport failure the shared sender logs the destination URL rather than the app slug.Validation
just check-containergreen:cargo fmt --all --check,cargo clippy --workspace --all-targets -- -D warnings,cargo test --workspace --all-targets.#DEV-527