Skip to content

ci(config): add automated stale configuration detection utility (#722) - #726

Open
ravendevhub wants to merge 1 commit into
Core-Foundry:mainfrom
ravendevhub:ci/stale-config-detection-722
Open

ci(config): add automated stale configuration detection utility (#722)#726
ravendevhub wants to merge 1 commit into
Core-Foundry:mainfrom
ravendevhub:ci/stale-config-detection-722

Conversation

@ravendevhub

Copy link
Copy Markdown

Summary

Resolves #722 by implementing an automated scanner (scripts/detect-stale-config.py) that verifies all configuration keys in .env.example against active references across the Listener, Dashboard, Smart Contracts, and Docker Compose files.

Changes

  1. Config Scanner (scripts/detect-stale-config.py):
    • Parses variables from .env.example.
    • Searches listener/src, dashboard/src, contract/src, docker-compose.yml, and scripts for active usage patterns (process.env, import.meta.env, ${VAR}, env::var).
    • Includes configurable allowlist for CI/CD and external platform variables.
  2. Documentation (docs/STALE_CONFIG_DETECTION.md):
    • Details usage instructions and allowlist policy.

Acceptance Criteria

  • Documented configuration fields can be compared against actual usage.
  • Potentially obsolete variables are reported.
  • The check can be run locally or through CI.
  • False positives are documented where unavoidable.

…-Foundry#722)

- Extract documented environment keys from .env.example
- Scan listener, dashboard, smart contract, and docker compose codebases for active references
- Provide allowlist for CI/CD and external platform variables to eliminate false positives
- Document usage and verification policy in docs/STALE_CONFIG_DETECTION.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Automated Stale Configuration Detection

1 participant