Capability Readiness
Capability readiness tells you which DevOps Genie workflows are usable for your organization right now.
Readiness inputs
DevOps Genie checks:
- Active cloud accounts.
- Whether the DevOps Genie Agent is connected.
- Whether the agent has sent a recent heartbeat.
- Which capabilities the agent reports from its configuration.
- Whether VCS access and repository URLs are configured for PR-based workflows.
Cloud-only capabilities
These can become ready with at least one connected cloud account:
- Cloud Resource Scanning.
- Compliance and Security Audit.
Agent-powered capabilities
These require a live agent and may require VCS configuration:
| Capability | Required setup |
|---|---|
| Terraform Code Generation | Agent, VCS auth, infrastructure repository URL. |
| Kubernetes Application Deployment | Agent, VCS auth, deployment repository URL. |
| CI/CD Pipeline Generation | Agent, VCS auth, at least one configured repository URL. |
| Cost Analysis and Optimization | Agent and a connected cloud account. VCS is needed for PR-based changes. |
If a capability is partial
Open the capability detail page in Integrations > Capabilities. It shows which prerequisites are satisfied and what is missing.
Common causes:
- Agent pod is not connected.
- Agent heartbeat is stale.
- VCS token or GitHub App credentials are missing.
- Repository URL is missing.
- The agent was installed before the latest configuration change and needs a Helm upgrade or restart.