refactor(observability): consume dunite-core error-log + client-IP #495
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/DEV-529-consume-observability"
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 dunite-core's error-log ring + trusted-proxy client-IP (dunite #39, DEV-529) and removes bunyip's copies.
error_log.rs-> a re-export shim overdunite_core::error_log(ErrorLogBuffer/ErrorLogLayer/ErrorLogEntry/DEFAULT_CAPACITY). Themain.rstracing wiring and the admin log view are unchanged.middleware/auth.rs:extract_client_ipkeeps its thin wrapper (it reads bunyip's trusted-proxy config viatrusted_proxies) but delegates todunite_core::middleware::client_ip. The localresolve_client_ipand its four unit tests are removed (the parity tests live in dunite-core). The ~30crate::middleware::extract_client_ipcall sites are unchanged.Pins
Bumps the dunite-core graph (core/download/oci/oidc)
90a828f->82f9baa(dunite-core gains error_log + client_ip; download/oci/oidc are unchanged). The leaf pins stay put, so this does not cross thedunite-user-coreMembershipTierrename.Validation
just check-containergreen:cargo fmt --all --check,cargo clippy --workspace --all-targets -- -D warnings,cargo test --workspace --all-targets.#DEV-529