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
//! Confium Store cloud KMS backends.
//!
//! This crate implements [`confium_store::backend::StoreBackend`] for the
//! three major cloud key management services:
//!
//! - **AWS Key Management Service** (feature `aws-kms`)
//! - **Google Cloud Key Management Service** (feature `gcp-kms`)
//! - **Azure Key Vault** (feature `azure-keyvault`)
//!
//! Each backend lives behind its own Cargo feature so consumers can pull
//! in only the SDK they need. With no features enabled the crate compiles
//! to nothing — it exists purely to host the three backends. See
//! `TODO.roadmap/18-hardware-keystore-backends.md` for the design.
//!
//! # Wire names
//!
//! Backends register under the wire names `"aws-kms"`, `"gcp-kms"` and
//! `"azure-keyvault"`. Pass these to `cfm_keystore_create` (or to
//! [`confium_store::Keystore::new`]) once this crate is linked into the
//! process; the link-time inventory takes care of registration.
//!
//! # KMS API status
//!
//! Client construction is real for all three providers (credentials,
//! region/endpoint/project/vault resolution; lazy on first use).
//! `aws-kms` additionally lists real KMS key IDs via `ListKeys` in
//! `enumerate` (remote keys carry no local handle — the index string
//! is the KMS key ID). Secret/public put/get remain
//! [`confium_store::error::Error::NotImplemented`] pending the
//! `cfmp_sign_with_handle` plugin contract from TODO #03 — cloud KMS
//! providers never export private key material, so remote sign is the
//! only path for KMS-held keys.
// Re-export the active backend factory types so consumers can construct
// them directly without depending on the per-feature module path. Each
// alias is only present when its feature is enabled, mirroring how the
// backends are conditionally compiled.
pub use AwsKmsBackend;
pub use AzureKeyVaultBackend;
pub use GcpKmsBackend;