check-config

Validate Redis config store keys by running a CLI-driven diagnostic check from the repository root to inspect critical keys like processing_prefs, webhook_config, and routing_rules. This ensures configuration integrity and flags any drift across your environments.

Diagnose configuration drift by executing scripted checks that compare critical config keys across Redis and file storage. The process validates runtime flags and provides an audit trail of any inconsistencies found during the inspection.

Remediate invalid webhook_config or routing_rules keys by following guided correction commands provided after the diagnostic check. You apply the suggested fixes, re-run the validation scripts, and confirm the config store status is healthy.

Yes, you need a specific virtual environment and must execute the CLI-driven workflow from the repository root path. This setup ensures the scripted checks and optional API validation can properly access and inspect your file and Redis storage.

Yes, you can check both Redis and file-based config storage simultaneously. The diagnostic workflow validates configuration state and consistency across both storage types to ensure comprehensive inspection of your critical runtime settings.

Processing_prefs settings may not apply correctly due to configuration drift or invalid keys in the store. Run a config store health check to inspect the keys, identify inconsistencies, and follow the guided remediation steps to correct the state.