grpc_graphql_gateway 1.2.4

A Rust implementation of gRPC-GraphQL gateway - generates GraphQL execution code from gRPC services
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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81

# Graceful Shutdown

Enable production-ready server lifecycle management with graceful shutdown.

## Enabling Graceful Shutdown

```rust
use grpc_graphql_gateway::{Gateway, ShutdownConfig};
use std::time::Duration;

let gateway = Gateway::builder()
    .with_descriptor_set_bytes(DESCRIPTORS)
    .with_graceful_shutdown(ShutdownConfig {
        timeout: Duration::from_secs(30),          // Wait up to 30s
        handle_signals: true,                       // Handle SIGTERM/SIGINT
        force_shutdown_delay: Duration::from_secs(5),
    })
    .build()?;

gateway.serve("0.0.0.0:8888").await?;
```

## How It Works

1. **Signal Received**: SIGTERM, SIGINT, or Ctrl+C is received
2. **Stop Accepting**: Server stops accepting new connections
3. **Drain Requests**: In-flight requests are allowed to complete
4. **Cleanup**: Active subscriptions cancelled, resources released
5. **Exit**: Server shuts down gracefully

## Configuration Options

| Option | Type | Default | Description |
|--------|------|---------|-------------|
| `timeout` | Duration | 30s | Max wait for in-flight requests |
| `handle_signals` | bool | true | Handle OS signals automatically |
| `force_shutdown_delay` | Duration | 5s | Wait before forcing shutdown |

## Custom Shutdown Signal

Trigger shutdown from your own logic:

```rust
use tokio::sync::oneshot;

let (tx, rx) = oneshot::channel::<()>();

// Trigger shutdown after some condition
tokio::spawn(async move {
    tokio::time::sleep(Duration::from_secs(60)).await;
    let _ = tx.send(());
});

Gateway::builder()
    .with_descriptor_set_bytes(DESCRIPTORS)
    .serve_with_shutdown("0.0.0.0:8888", async { let _ = rx.await; })
    .await?;
```

## Kubernetes Integration

The gateway responds correctly to Kubernetes termination:

```yaml
spec:
  terminationGracePeriodSeconds: 30
  containers:
    - name: gateway
      lifecycle:
        preStop:
          exec:
            command: ["sleep", "5"]
```

## Benefits

- ✅ No dropped requests during deployment
- ✅ Automatic OS signal handling
- ✅ Configurable drain timeout
- ✅ Active subscription cleanup
- ✅ Kubernetes-compatible