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
//! Rust client for [signet](https://github.com/bytepunx/signet).
//!
//! Two connection modes mirror the two listeners signet exposes:
//! - [`dial_workload`](client::dial_workload) connects to the workload-facing
//! `SecretsService` using SPIFFE mTLS, the same credential mechanism the
//! signet server itself uses to authenticate callers. Gated behind the
//! `spiffe-workload` feature — see the crate README for why, and for the
//! fallback path (bring your own `tonic::transport::Channel`) when it's
//! disabled.
//! - [`dial_admin`](client::dial_admin) connects to the operator-facing
//! `AdminService`/`GitOpsService` using a bearer token over TLS (or
//! plaintext for loopback addresses), mirroring signet's own `signet`
//! CLI.
//!
//! [`watch_bundle`](restart::watch_bundle), [`acquire_lock`](restart::acquire_lock),
//! and [`wait_for_restart`](restart::wait_for_restart) implement signet's
//! coordinated-restart protocol: a service can watch for its own bundle
//! changes and safely serialize a fleet-wide restart via signet's distributed
//! restart lock, without a process host and without ever writing secrets to
//! the environment or disk. See `README.md`'s "Coordinated restarts" section
//! for the full design rationale, mirrored from the Go client.
//!
//! [`encrypt_for_secret`](sops_encrypt::encrypt_for_secret) produces
//! SOPS-compatible encrypted ciphertext for a secret value, since signetd
//! never encrypts on a client's behalf (`SyncBundle`/`TriggerSync` require
//! content already be real SOPS ciphertext). Mirrors `go/sops_encrypt.go`.
/// Generated protobuf/tonic bindings for signet, from bytepunx/signet-proto.
/// Run `buf generate` to regenerate `src/gen`.
// Each base file ends with its own `include!` of the matching *.tonic.rs
// file, so only the base file needs including here.
pub use ;
pub use dial_workload;
pub use ;
pub use ;