-
Notifications
You must be signed in to change notification settings - Fork 0
Priority Certified Connectors
Huzefaaa2 edited this page Jul 4, 2026
·
1 revision
CAVRA R4.2 adds a public-safe certified connector registry for the first priority provider wave. It builds on the R4.1 connector SDK and covers SCM, CI/CD, SIEM, ITSM, and ChatOps providers.
| Group | Providers |
|---|---|
| SCM | GitHub, GitLab, Azure Repos |
| CI/CD | GitHub Actions, Jenkins |
| SIEM | Splunk, Microsoft Sentinel |
| ITSM | ServiceNow, Jira |
| ChatOps | Slack, Microsoft Teams |
- Versioned certified connector manifests under
examples/connectors/priority-certified/. - Built-in registry and compatibility matrix in
src/cavra/certified_connectors.py. - Readiness packet validator in
scripts/validate_priority_connectors.py. - Delivery request-spec support for GitHub, GitLab, Azure Repos, GitHub Actions, and Jenkins in addition to the existing Splunk, Sentinel, ServiceNow, Jira, Slack, and Teams paths.
- Sample and sanitized live evidence packets.
- Strict CI workflow and tests.
python3 scripts/validate_priority_connectors.py --registry
python3 scripts/validate_priority_connectors.py --manifest-dir examples/connectors/priority-certified
python3 scripts/validate_priority_connectors.py --packet examples/connectors/enterprise-priority-connectors.sample.json
python3 scripts/validate_priority_connectors.py --packet examples/connectors/enterprise-priority-connectors.live.sanitized.example.json --require-live
python3 -m pytest tests/test_certified_connectors.py -qThe public repository now certifies the manifest contract, provider coverage, compatibility matrix, request-spec generation, credential redaction behavior, and readiness packet shape. Customer production use still requires tenant-specific credential custody, provider sandbox evidence, firewall allowlisting, webhook or token rotation, and support ownership records.
CAVRA Field Compass
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
| Start | Build | Operate | Assure |
|---|---|---|---|
| Quick Start | CLI | Enterprise Guide | AISPM |
| Reader Paths | Policy Syntax | Deployments | Evidence |
| Community | GUI | Troubleshooting | Conclusion |
Textbook home: Before the Agent Acts |
Development archive: development and testing artifacts |
Source repository: github.com/Huzefaaa2/cavra
- Foreword And Reader Paths
- Why CAVRA Exists
- Runtime Authority Model
- Architecture
- Editions
- Install And Deploy
- Community Guide
- Enterprise Guide
- CLI Reference
- GUI And Sandbox
- AISPM Guide
- Policy And Evidence
- Operations And Integrations
- Labs And Use Cases
- Appendices And FAQ
- Policy Language Reference
- Troubleshooting Playbook
- Technology Stack
- Unified Enterprise Roadmap
- Conclusion
- Development And Testing Archive
- Unified Enterprise Roadmap
- CLI
- API
- CAVRA Trial Field Guide
- AISPM Enterprise Live Ingestion
- Enterprise HA/DR Readiness
- Enterprise HA/DR Azure Map
- Enterprise KMS/HSM Evidence Custody
- Enterprise Immutable Audit Log
- Enterprise Compliance Mapping Packs
- Enterprise Reporting Exports
- Connector SDK And Certification
- Priority Certified Connectors
- Model Registry Connectors