-
Notifications
You must be signed in to change notification settings - Fork 0
Connector Execution Hooks
Huzefaaa2 edited this page May 19, 2026
·
4 revisions
CAVRA supports live connector execution hooks for SIEM, ChatOps, ITSM, and generic webhooks.
- Splunk HEC
- Microsoft Sentinel or Log Analytics ingestion endpoints
- Datadog Logs
- Slack incoming webhooks
- Microsoft Teams incoming webhooks
- Jira issue API
- ServiceNow change request API
- Generic webhooks
Use examples/connectors/cavra-connectors.example.json. Set CAVRA_CONNECTOR_CONFIG for the API and CLI.
Secrets should come from environment variables through token_env, api_key_env, authorization_env, or url_env.
POST /integrations/{integration_id}/deliverPOST /promotion-executions/{execution_id}/audit-export/deliverPOST /rollback-executions/{rollback_id}/deliver
The integration endpoint loads the integration record, uses its provider by default, sends the event through the configured connector, and returns redacted delivery evidence. Release governance endpoints deliver promotion audit exports and rollback execution records through the same connector layer.
cavra integration deliver .cavra/evidence/latest/siem-event.json --config .cavra/connectors.json --provider splunk
cavra release deliver-promotion-audit .cavra/release/rollout-promotion-execution/rollout-promotion-execution.json --config .cavra/connectors.json --provider webhook --retries 1
cavra release deliver-rollback-execution .cavra/release/rollout-rollback-execution/rollout-rollback-execution.json --config .cavra/connectors.json --provider webhook --retries 1- As a SOC analyst, I can receive CAVRA evidence in SIEM.
- As a platform engineer, I can notify Slack or Teams with redacted evidence.
- As a change manager, I can create Jira or ServiceNow records.
- As a release manager, I can deliver promotion audit and rollback execution records with retry evidence.
- As an auditor, I can inspect delivery attempts without seeing secrets.
Connector hooks make CAVRA operational inside enterprise systems of record rather than stopping at generated payload files.
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
- Conclusion