How does Diagrid Catalyst handle Dapr component configuration drift across multiple cloud providers?

Catalyst uses a centralized component management approach where you define Dapr component YAMLs (state stores, pub/sub, bindings) once and apply them consistently via the Catalyst API or console. It supports environment-specific overrides for provider-specific settings (e.g., AWS DynamoDB vs Azure Cosmos DB) while keeping the logical component configuration uniform. Catalyst audits component changes and can roll back misconfigurations. This prevents drift by enforcing a single source of truth for component definitions across clouds.