Expand description
Core signer domain model and business logic.
This module provides the central Signer
type that represents signers
throughout the relayer system, including:
- Domain Model: Core
Signer
struct with validation and configuration - Business Logic: Update operations and validation rules
- Error Handling: Comprehensive validation error types
- Interoperability: Conversions between API, config, and repository representations
The signer model supports multiple signer types including local keys, AWS KMS, Google Cloud KMS, Vault, and Turnkey service integrations.
Structs§
- AwsKms
Signer Config - AWS KMS signer configuration The configuration supports:
- AwsKms
Signer Config Storage - Storage representations for other signer types (these are simpler as they don’t contain secrets that need encoding)
- AwsKms
Signer File Config - AwsKms
Signer Request Config - AWS KMS signer configuration for API requests
- Google
Cloud KmsKey File Config - Google
Cloud KmsService Account File Config - Google
Cloud KmsSigner Config - Google Cloud KMS signer configuration
- Google
Cloud KmsSigner Config Storage - Google
Cloud KmsSigner File Config - Google
Cloud KmsSigner KeyConfig - Google Cloud KMS key configuration
- Google
Cloud KmsSigner KeyConfig Storage - Google
Cloud KmsSigner KeyRequest Config - Google Cloud KMS key configuration for API requests
- Google
Cloud KmsSigner KeyResponse Config - Google
Cloud KmsSigner Request Config - Google Cloud KMS signer configuration for API requests
- Google
Cloud KmsSigner Service Account Config - Google Cloud KMS service account configuration
- Google
Cloud KmsSigner Service Account Config Storage - Google
Cloud KmsSigner Service Account Request Config - Google Cloud KMS service account configuration for API requests
- Google
Cloud KmsSigner Service Account Response Config - Local
Signer Config - Local signer configuration for storing private keys
- Local
Signer Config Storage - Local signer configuration for storage (with base64 encoding)
- Local
Signer File Config - Local
Signer Request Config - Local signer configuration for API requests
- Signer
- Core signer domain model containing both metadata and configuration
- Signer
Create Request - Request model for creating a new signer
- Signer
File Config - Individual signer configuration from config file
- Signer
Repo Model - Repository model for signer storage and retrieval
- Signer
Response - Signer
Update Request - Request model for updating an existing signer At the moment, we don’t allow updating signers
- Signers
File Config - Collection of signer configurations
- Turnkey
Signer Config - Turnkey signer configuration
- Turnkey
Signer Config Storage - Turnkey
Signer File Config - Turnkey
Signer Request Config - Turnkey signer configuration for API requests
- Vault
Signer Config - Vault signer configuration
- Vault
Signer Config Storage - Vault
Signer File Config - Vault
Signer Request Config - Vault signer configuration for API requests
- Vault
Transit Signer Config - Vault Transit signer configuration
- Vault
Transit Signer Config Storage - Vault
Transit Signer File Config - Vault
Transit Signer Request Config - Vault Transit signer configuration for API requests
Enums§
- Signer
Config - Domain signer configuration enum containing all supported signer types
- Signer
Config Request - Signer configuration enum for API requests (without type discriminator)
- Signer
Config Response - Signer configuration response Does not include sensitive information like private keys
- Signer
Config Storage - Signer
File Config Enum - Main enum for all signer config types
- Signer
Type - Signer type enum used for validation and API responses
- Signer
Type Request - Signer type enum for API requests
- Signer
Validation Error - Validation errors for signers