config-consistency-checker

To detect configuration drift between staging and production, you can compare key-value pairs across files like staging.yaml and production.yaml to classify differences as intentional changes or drift. The checker flags missing keys, drifted values, and type mismatches before deployment.

Configuration drift occurs when environment files or deployment manifests like Kubernetes ConfigMaps become inconsistent over time due to manual edits. This drift causes deployment failures when missing configuration keys or type mismatches break applications moving from staging to production.

Yes, you can audit code against configuration files to find dead configuration keys that exist in files but are never read by code, and unbacked reads where code reads configuration keys that are missing from the files.

You can check Kubernetes deployment manifests against application configuration by comparing the flattened key-value pairs and types in your ConfigMaps against your application config files to identify and flag any deployment drift or mismatches.

The best way to prevent works in staging but broken in prod scenarios is to run a consistency check comparing flattened key-value pairs and types across configuration files and deployment manifests to catch missing keys and type mismatches before production deployment.