summaryrefslogtreecommitdiff
path: root/vendor/hyper/src/body/mod.rs
diff options
context:
space:
mode:
authormo khan <mo@mokhan.ca>2025-07-15 16:37:08 -0600
committermo khan <mo@mokhan.ca>2025-07-17 16:30:22 -0600
commit45df4d0d9b577fecee798d672695fe24ff57fb1b (patch)
tree1b99bf645035b58e0d6db08c7a83521f41f7a75b /vendor/hyper/src/body/mod.rs
parentf94f79608393d4ab127db63cc41668445ef6b243 (diff)
feat: migrate from Cedar to SpiceDB authorization system
This is a major architectural change that replaces the Cedar policy-based authorization system with SpiceDB's relation-based authorization. Key changes: - Migrate from Rust to Go implementation - Replace Cedar policies with SpiceDB schema and relationships - Switch from envoy `ext_authz` with Cedar to SpiceDB permission checks - Update build system and dependencies for Go ecosystem - Maintain Envoy integration for external authorization This change enables more flexible permission modeling through SpiceDB's Google Zanzibar inspired relation-based system, supporting complex hierarchical permissions that were difficult to express in Cedar. Breaking change: Existing Cedar policies and Rust-based configuration will no longer work and need to be migrated to SpiceDB schema.
Diffstat (limited to 'vendor/hyper/src/body/mod.rs')
-rw-r--r--vendor/hyper/src/body/mod.rs50
1 files changed, 0 insertions, 50 deletions
diff --git a/vendor/hyper/src/body/mod.rs b/vendor/hyper/src/body/mod.rs
deleted file mode 100644
index 7b71d98b..00000000
--- a/vendor/hyper/src/body/mod.rs
+++ /dev/null
@@ -1,50 +0,0 @@
-//! Streaming bodies for Requests and Responses
-//!
-//! For both [Clients](crate::client) and [Servers](crate::server), requests and
-//! responses use streaming bodies, instead of complete buffering. This
-//! allows applications to not use memory they don't need, and allows exerting
-//! back-pressure on connections by only reading when asked.
-//!
-//! There are two pieces to this in hyper:
-//!
-//! - **The [`Body`] trait** describes all possible bodies.
-//! hyper allows any body type that implements `Body`, allowing
-//! applications to have fine-grained control over their streaming.
-//! - **The [`Incoming`] concrete type**, which is an implementation
-//! of `Body`, and returned by hyper as a "receive stream" (so, for server
-//! requests and client responses).
-//!
-//! There are additional implementations available in [`http-body-util`][],
-//! such as a `Full` or `Empty` body.
-//!
-//! [`http-body-util`]: https://docs.rs/http-body-util
-
-pub use bytes::{Buf, Bytes};
-pub use http_body::Body;
-pub use http_body::Frame;
-pub use http_body::SizeHint;
-
-pub use self::incoming::Incoming;
-
-#[cfg(all(any(feature = "client", feature = "server"), feature = "http1"))]
-pub(crate) use self::incoming::Sender;
-#[cfg(all(
- any(feature = "http1", feature = "http2"),
- any(feature = "client", feature = "server")
-))]
-pub(crate) use self::length::DecodedLength;
-
-mod incoming;
-#[cfg(all(
- any(feature = "http1", feature = "http2"),
- any(feature = "client", feature = "server")
-))]
-mod length;
-
-fn _assert_send_sync() {
- fn _assert_send<T: Send>() {}
- fn _assert_sync<T: Sync>() {}
-
- _assert_send::<Incoming>();
- _assert_sync::<Incoming>();
-}