Integrate BACKBEAT SDK and resolve KACHING license validation
Major integrations and fixes: - Added BACKBEAT SDK integration for P2P operation timing - Implemented beat-aware status tracking for distributed operations - Added Docker secrets support for secure license management - Resolved KACHING license validation via HTTPS/TLS - Updated docker-compose configuration for clean stack deployment - Disabled rollback policies to prevent deployment failures - Added license credential storage (CHORUS-DEV-MULTI-001) Technical improvements: - BACKBEAT P2P operation tracking with phase management - Enhanced configuration system with file-based secrets - Improved error handling for license validation - Clean separation of KACHING and CHORUS deployment stacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -4,9 +4,9 @@ import (
|
||||
"context"
|
||||
"time"
|
||||
|
||||
"chorus.services/bzzz/pkg/security"
|
||||
"chorus.services/bzzz/pkg/ucxl"
|
||||
slurpContext "chorus.services/bzzz/pkg/slurp/context"
|
||||
"chorus/pkg/security"
|
||||
"chorus/pkg/ucxl"
|
||||
slurpContext "chorus/pkg/slurp/context"
|
||||
)
|
||||
|
||||
// RoleManager handles definition and management of roles and permissions
|
||||
@@ -184,7 +184,7 @@ type AuditLogger interface {
|
||||
// EncryptionManager handles role-based encryption and key management
|
||||
//
|
||||
// Manages encryption keys and operations for role-based access control,
|
||||
// integrating with the BZZZ crypto system for secure context storage
|
||||
// integrating with the CHORUS crypto system for secure context storage
|
||||
// and distribution.
|
||||
type EncryptionManager interface {
|
||||
// EncryptForRoles encrypts context data for specific roles
|
||||
|
||||
Reference in New Issue
Block a user