[oblt-aw] Control Plane Dashboard
Author: elastic-vault-github-plugin-prod[bot]Created Sep 16, 2026Updated Sep 18, 2026
Labelsneeds_teamoblt-aw/dashboard
Control Plane Dashboard
Use this dashboard to enable or disable agentic workflows for this repository. Click the checkboxes below to toggle workflows on or off.
Observability (obs)
| Workflow | Maturity | Description |
|---|---|---|
| Agent Suggestions | experimental | Suggests agentic workflows and improvements for the repository based on analysis of current setup. inner-workflows: obs-aw-agent-suggestions.yml |
| Automated Documentation | stable | Analyzes documentation for gaps, outdated content, and inconsistencies; creates issues and PRs to improve docs. inner-workflows: obs-aw-autodoc.yml |
| Automerge | stable | Enables auto-merge for allowed bot PRs (same authors as dependency-review) with oblt-aw/ai/merge-ready when validation and approval gates pass; GitHub enforces required checks at merge time. inner-workflows: obs-aw-automerge.yml |
| Dependency Review | stable | Analyzes dependency-update PRs from bots, applies merge-ready labels when criteria are met. inner-workflows: obs-aw-dependency-review.yml |
| Duplicate Issue Detector | experimental | Detects potential duplicate issues when a new issue is opened or when the entrypoint is run manually. inner-workflows: obs-aw-duplicate-issue-detector.yml |
| Issue Triage | early-adoption | Triages newly opened issues using the generic issue-triage agentic workflow. inner-workflows: obs-aw-issue-triage.yml |
| Issue Fixer | experimental | Executes generic issue fixes requested with /ai implement comments, excluding specialized security and resource-not-accessible flows. inner-workflows: obs-aw-issue-fixer.yml |
| Mention in Issue | early-adoption | AI assistant for issues — answers questions, debugs problems, and creates PRs on demand when triggered with a /ai comment. inner-workflows: obs-aw-mention-in-issue.yml |
| Security | early-adoption | Runs static security checks on workflows, shell scripts, and dependency manifests per the security scanning ruleset; opens issues for findings. inner-workflows: obs-aw-security-fixer.yml, obs-aw-security-issue-superseder.yml, obs-aw-security-triage.yml, obs-aw-security-injection-detector.yml, obs-aw-security-supply-chain-detector.yml, obs-aw-security-secrets-detector.yml, obs-aw-security-least-privilege-detector.yml |
| Resource Not Accessible by Integration | early-adoption | Detects 'Resource not accessible by integration' occurrences in workflow logs, creates triage issues, triages newly opened issues, and executes fixes for issues labeled ready to fix. inner-workflows: obs-aw-resource-not-accessible-by-integration-detector.yml, obs-aw-resource-not-accessible-by-integration-fixer.yml, obs-aw-resource-not-accessible-by-integration-triage.yml |
| PR Buildkite Detective | stable | Analyzes Buildkite CI failures for a PR when a Buildkite status check fails; posts a diagnostic comment on the pull request. inner-workflows: obs-aw-estc-pr-buildkite-detective.yml |
Enable / Disable
Click a checkbox to enable or disable a workflow:
- Agent Suggestions
- Automated Documentation
- Automerge
- GitHub Actions bumps
- pre-commit hook updates
- Python dependencies
- Go dependencies
- Update beats
- Node dependencies
- Terraform / OpenTofu
- Open Policy Agent
- VM / container images
- Package version
- Dependency Review
- Duplicate Issue Detector
- Issue Triage
- Issue Fixer
- Mention in Issue
- Security
- Injection Detection
- Supply-chain Hardening
- Secret Management
- Least Privilege
- Resource Not Accessible by Integration
- PR Buildkite Detective
Instructions
- Enable a workflow: Check the checkbox next to the workflow.
- Disable a workflow: Uncheck the checkbox, then reply on this issue with a short deactivation reason (an audit comment will ask for it and mention @elastic/observablt-ci).
- Sub-features: Indented checkboxes under a parent refine which parts of that workflow run. Sub-features take effect only while the parent workflow checkbox is enabled.
- Audit trail: Enable/disable changes are recorded as comments on this issue (when / what / who).
- Changes are applied at runtime when the client runs.
Source: elastic/beats