cratestack-client-rust 0.7.7

Rust-native schema-first framework for typed HTTP APIs, generated clients, and backend services.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

use crate::error::ClientError;

#[derive(Debug, Clone, PartialEq, Eq)]
pub struct AuthorizationRequest {
    pub method: String,
    pub path: String,
    pub canonical_query: Option<String>,
    pub content_type: Option<String>,
    pub body: Vec<u8>,
    pub canonical_request: String,
}

/// Async by design (issue #453): real credential providers — an OAuth2
/// client-credentials token with a refresh-on-expiry cache, for instance —
/// need to make an HTTP call on a cache miss, which a sync `authorize`
/// can't do without `block_on` (panics/deadlocks depending on the runtime)
/// or a pre-fetch-and-stash workaround that reintroduces the expiry race
/// the cache existed to avoid. `#[async_trait]` (rather than a bare
/// `async fn` in the trait) keeps `Arc<dyn RequestAuthorizer>` — both
/// `CratestackClient::with_request_authorizer` and
/// `CratestackGrpcClient::with_request_authorizer` store the authorizer as
/// a trait object — dyn-compatible; native AFIT would drop that. Same
/// convention other dyn-dispatched async hook traits already use elsewhere
/// in the workspace (e.g. `cratestack_core::audit::AuditSink`).
#[async_trait::async_trait]
pub trait RequestAuthorizer: Send + Sync {
    async fn authorize(
        &self,
        request: &AuthorizationRequest,
    ) -> Result<Vec<(String, String)>, ClientError>;
}