refactor(csrf): consume dunite-core OriginGuard, drop bunyip-api copy #493
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/DEV-526-consume-dunite-csrf"
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-core CSRF guard (dunite #36, DEV-526) and removes bunyip-api's local copy.
dunite-coredirectly;main.rswiresdunite_core::middleware::OriginGuard::new(&cors_origins, &CSRF_EXEMPT_PREFIXES, &CSRF_AMBIENT_COOKIES)./oauth2/,/.well-known/,/v1/webhooks/stripe; ambient cookiesaccess_token,refresh_token.bunyip-api/src/csrf.rs(385 LOC) and itspub mod csrf;are deleted; the eleven guard tests now live in dunite-core.Pins
The dunite-core graph (
dunite-core,dunite-download,dunite-oci,dunite-oidc) moves to90a828fas one rev so a single dunite-core resolves. The independent leaf crates (dunite-user-core,dunite-stripe-core,dunite-stripe,dunite-feedback,dunite-geoip,dunite-ipenrich,dunite-image-upload) stay atae62c27. This is deliberate: it does NOT cross dunite's unrelatedSubscriptionTier->MembershipTierrename (dunite #35), which is the bunyip-side BUNYIP-488's job.Validation
just check-containergreen in the pinned rust-builder image:cargo fmt --all --check,cargo clippy --workspace --all-targets -- -D warnings,cargo test --workspace --all-targets- every suite 0 failed. Net -367 lines.#DEV-526