Files
openobserve/.github/workflows
Shrinath RaoandClaude Opus 4.8 6f1d2094c6 ci: E2E Council — thin caller + retire legacy workflow (#12886)
## E2E Council — thin caller + retire legacy workflow

Cutover to the **DocGen topology**: the heavy E2E Council engine now
lives in the private `o2-enterprise` repo
(openobserve/o2-enterprise#2019); this OSS repo keeps only a **thin
caller** that dispatches it.

### What's here
- **NEW** `.github/workflows/e2e-council-caller.yml` — thin caller.
Three doors: `workflow_dispatch`, `issue_comment` (`/e2e`,
`/e2e-dryrun`, org-member gated), and `pull_request: [closed]`
auto-on-merge (behind `vars.E2E_AUTO_ON_MERGE`). Gates the commenter,
resolves pr/dry_run/clobber/actor, then `gh workflow run e2e-council.yml
--repo openobserve/o2-enterprise` via `secrets.ORG_ADMIN_TOKEN`, and
acks on the OSS PR.
- **RENAMED** `e2e-council.yml` → `e2e-council-legacy.yml` — header
marked RETIRED, triggers reduced to `workflow_dispatch`-only (manual
fallback) so it can't double-fire with the caller. Agent assets
intentionally kept so the legacy fallback still runs; delete once the
ENT engine is proven.

### Why dispatch (not `workflow_call`)
A cross-repo reusable call needs an ENT Actions access policy; a PAT
with `Actions: R/W` can `workflow_dispatch` with none. Mirrors DocGen.

### Rollout note
The `/e2e` comment path only takes effect once this caller is on `main`
(comment/dispatch triggers read from the default branch). Until then,
test the engine directly via `workflow_dispatch --ref` on the ENT PR.

Paired with the engine PR: openobserve/o2-enterprise#2019

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-25 14:21:06 +00:00
..
2026-06-02 03:58:01 +00:00
2026-06-05 13:09:23 +00:00
2026-06-02 03:58:01 +00:00