chore: refactor integrations#1165
Conversation
Signed-off-by: vaibhav upreti <[email protected]>
Greptile SummaryThis refactoring splits Confidence Score: 4/5Safe to merge with awareness that the verification layer migration is incomplete — verify_integrations() still uses its own parallel registry, not the new registry.VERIFIER_REGISTRY. All existing functionality is preserved; the split of catalog.py, extraction of config models, and addition of probe_access() methods are clean. The structural concern is that registry.VERIFIER_REGISTRY (validated by tests) is never consumed by the actual verify_integrations() production path, creating a gap between tested and running code. The env_int isdigit issue is obscure but real. No data loss or security issues were found. app/integrations/registry.py and app/integrations/verify.py — two parallel VERIFIER_REGISTRY definitions where only verify.py's is used in production, but tests/integrations/test_registry.py validates only registry.py's. app/integrations/_relational.py env_int() isdigit bug. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
CLI["cli.py\ncmd_verify()"]
VFY["verify.py\nverify_integrations()"]
VFY_REG["verify.py\nVERIFIER_REGISTRY\n(inline _verify_* fns)"]
REG["registry.py\nINTEGRATION_SPECS\n+ VERIFIER_REGISTRY"]
ADAPTERS["_verification_adapters.py\nbuild_probe_verifier()\nbuild_validation_verifier()"]
CLIENTS["Service Clients\n(probe_access())"]
CATALOG["catalog.py → _catalog_impl.py\nclassify / resolve integrations"]
CFGMODELS["config_models.py\nPydantic config models"]
MODELS["models.py\n(re-exports → config_models.py)"]
TEST["test_registry.py\nasserts VERIFIER_REGISTRY\n== SUPPORTED_VERIFY_SERVICES"]
CLI -->|"imports SUPPORTED_SETUP_SERVICES"| REG
CLI -->|"calls"| VFY
VFY -->|"uses"| VFY_REG
VFY -->|"imports SUPPORTED_VERIFY_SERVICES\nCORE_VERIFY_SERVICES"| REG
REG -->|"builds VERIFIER_REGISTRY from"| ADAPTERS
ADAPTERS -->|"delegates to"| CLIENTS
CATALOG -->|"uses family_key, service_key, etc."| REG
CFGMODELS -->|"re-exported by"| MODELS
TEST -->|"checks registry.VERIFIER_REGISTRY"| REG
style VFY_REG fill:#ffcccc,stroke:#cc0000
style ADAPTERS fill:#fff3cd,stroke:#cc8800
style REG fill:#fff3cd,stroke:#cc8800
style TEST fill:#ffcccc,stroke:#cc0000
subgraph gap["Gap: registry.VERIFIER_REGISTRY built but never used in production"]
REG
ADAPTERS
end
Reviews (1): Last reviewed commit: "chore: refactor integrations" | Re-trigger Greptile |
… reusable validators.
|
🌊 Merged. @VaibhavUpreti is now permanently woven into git history. No take-backs. 😄 👋 Join us on Discord - OpenSRE : hang out, contribute, or hunt for features and issues. Everyone's welcome. |
Resolves conflicts in auto-generated bot files: docs/daily-updates/overview.mdx, docs/daily-updates/2026-04-30.mdx, docs/daily-updates/2026-05-01.mdx, and README.md (contributors section). All four are produced by scheduled bot workflows in main and have no relationship to this PR; resolved by accepting the upstream main version verbatim. Pulls in 35+ commits from main since this PR was opened, including: refactor of integrations module (Tracer-Cloud#1165), Splunk integration (Tracer-Cloud#791), interactive shell improvements (Tracer-Cloud#1159, Tracer-Cloud#1167), Claude Code CLI provider (Tracer-Cloud#1168), and CI quality gate restoration. None of these touch the OpenSearch wizard, detect_sources, or the validation modules this PR modifies. Refs: Tracer-Cloud#1143

refactor the integrations catalogue and module