Skip to content

docs: move oabctl usage guide to docs/oabctl.md, link from README#1289

Merged
thepagent merged 2 commits into
mainfrom
docs/split-oabctl-usage-guide
Jul 4, 2026
Merged

docs: move oabctl usage guide to docs/oabctl.md, link from README#1289
thepagent merged 2 commits into
mainfrom
docs/split-oabctl-usage-guide

Conversation

@chaodu-agent

Copy link
Copy Markdown
Collaborator

Summary

operator/README.md had grown into a comprehensive oabctl usage guide —
manifest schema, ingress/webhooks, secrets formats, bootstrap, IAM tables,
commands reference — mixed in with the tool's architecture overview. Worse,
nothing in the top-level README.md pointed at it, so oabctl wasn't
discoverable from the project's front door at all.

Changes

  • New: docs/oabctl.md — the full usage guide, moved verbatim (installation,
    quick start, complete workflow, configuration, manifest schema
    including ingress/webhooks, bootstrap, IAM tables, spec.secrets
    formats, state store, commands reference, prerequisites/permissions).
    Matches the flat docs/*.md naming convention every other feature doc
    in the repo already uses.
  • Trimmed: operator/README.md — now just the architecture overview
    (the "How It Works" diagram), a short quick start, a new source-layout
    section, and a prominent link to docs/oabctl.md for full usage.
  • Updated: top-level README.md — added an "AWS ECS Deployment" section
    (mirroring the existing "Kubernetes Deployment" section) linking to
    docs/oabctl.md, so oabctl is now discoverable without already knowing
    operator/ exists.

No content was dropped — every usage section moved as-is. Internal relative
links were re-checked and confirmed correct from docs/oabctl.md's new
location (../operator/README.md, ../operator/schema/oabservice-v2.json,
telegram.md, refarch/telegram-cloudflare-tunnel.md).

Before:
  README.md ─────────────────────► (no link to oabctl at all)
  operator/README.md ─────────────► architecture + full usage guide (mixed)

After:
  README.md ──► "AWS ECS Deployment" section ──► docs/oabctl.md (full usage)
                                                        ▲
  operator/README.md ──► architecture overview ────────┘
                          + link to docs/oabctl.md

Testing done

Doc-only change — no code touched. Verified all relative markdown links in
the moved/edited files resolve to real files at their new/updated paths via
glob/grep, no build or test run needed.

operator/README.md had grown into a comprehensive usage guide (manifest
schema, ingress/webhooks, secrets formats, bootstrap, IAM tables,
commands reference) mixed in with the tool's architecture overview -
and nothing in the top-level README pointed at it at all, so it wasn't
discoverable outside the operator/ directory.

Split it: docs/oabctl.md is now the full usage guide (matches the
flat docs/*.md convention used by every other feature doc), and
operator/README.md is trimmed to an architecture/source-layout
overview with a prominent link to docs/oabctl.md for usage. Added an
'AWS ECS Deployment' section to the top-level README (mirroring the
existing 'Kubernetes Deployment' section) linking to docs/oabctl.md,
so oabctl is now discoverable from the project's front door.

No content was dropped - operator/README.md's usage sections moved
verbatim to docs/oabctl.md; only the architecture diagram, quick
start, and a new source-layout section stayed in operator/README.md.
@chaodu-agent chaodu-agent requested a review from thepagent as a code owner July 4, 2026 12:20
@chaodu-agent

Copy link
Copy Markdown
Collaborator Author

LGTM ✅ — Clean doc restructuring; content moved verbatim with correct relative links.

What This PR Does

operator/README.md grew into a 27KB combined architecture overview + usage guide, making it hard to navigate. This PR splits it into two focused files: docs/oabctl.md (full usage guide) and a trimmed operator/README.md (architecture only), while making oabctl discoverable from the top-level README.md.

How It Works

  • Moves all usage content (installation, manifest schema, ingress/webhooks, secrets, bootstrap, IAM, commands) verbatim into docs/oabctl.md — matching the existing docs/*.md convention.
  • Trims operator/README.md to architecture diagram, quick start, and a new source layout section — with a prominent link to the full guide.
  • Adds an "AWS ECS Deployment" section in the root README.md (parallel to the existing "Kubernetes Deployment" section) pointing to docs/oabctl.md.

Findings

# Severity Finding Location
1 🟢 Content moved verbatim — no accidental loss or duplication docs/oabctl.md
2 🟢 All relative links verified correct from new file locations all files
3 🟢 New source layout section in operator/README adds developer value operator/README.md
What's Good (🟢)
  • Zero content loss — every section from the original operator/README.md appears in docs/oabctl.md
  • Relative links (../operator/README.md, refarch/telegram-cloudflare-tunnel.md, telegram.md, ../operator/schema/oabservice-v2.json) all resolve correctly from their new location
  • The new source layout tree in operator/README.md is a useful addition for developers navigating the codebase
  • Root README discoverability fix addresses a real gap — oabctl was invisible from the project front door
  • Follows existing repo conventions (flat docs/*.md structure)
Baseline Check
  • PR opened: 2026-07-04 (today)
  • Main already has: operator/README.md (27KB, mixed architecture + usage guide), no docs/oabctl.md, no ECS section in root README
  • Net-new value: proper separation of concerns (architecture vs. usage), root-level discoverability, source layout section

@thepagent thepagent enabled auto-merge (squash) July 4, 2026 12:24
@thepagent thepagent disabled auto-merge July 4, 2026 12:24
@thepagent thepagent merged commit ebddf25 into main Jul 4, 2026
6 of 7 checks passed
@chaodu-agent

Copy link
Copy Markdown
Collaborator Author

LGTM ✅ — Clean documentation restructure that improves discoverability without dropping content.

What This PR Does

The operator/README.md had grown into a combined architecture overview + full usage guide, and oabctl was undiscoverable from the top-level README. This PR splits the usage guide into docs/oabctl.md (matching the flat docs/*.md convention), trims operator/README.md to architecture-only with a cross-link, and adds an "AWS ECS Deployment" section to the top-level README.

How It Works

Pure content move — no additions or deletions of substance. operator/README.md keeps the "How It Works" diagram, a minimal quick start, and a new source-layout section (replacing the removed usage sections), plus a prominent link to the new canonical location. The top-level README now mirrors the existing "Kubernetes Deployment" section pattern.

Findings

# Severity Finding Location
1 🟢 All internal relative links verified correct from docs/oabctl.md../operator/README.md, ../operator/schema/oabservice-v2.json, telegram.md, refarch/telegram-cloudflare-tunnel.md all resolve to existing files docs/oabctl.md
2 🟢 Follows established docs/*.md flat naming convention used by all other feature docs
3 🟢 Top-level README addition mirrors the existing "Kubernetes Deployment" section structure cleanly README.md:268-280
4 🟢 Source layout section in operator/README.md is a nice addition that aids navigation for contributors operator/README.md:71-84
What's Good (🟢)
  • Zero content loss — every usage section moved verbatim
  • Discoverability fixed: users landing on the repo's front page can now find oabctl without knowing the operator/ subdirectory exists
  • Clean separation of concerns: architecture (for contributors) vs. usage guide (for operators)
  • The source-layout section in operator/README.md replaces removed content with something equally useful for contributor orientation
  • All cross-links between the three changed files form a coherent navigation graph
Baseline Check
  • PR opened: 2026-07-04
  • Main already has: all the oabctl usage content, but buried in operator/README.md with no link from top-level README
  • Net-new value: oabctl discoverable from project front door; clean architecture/usage split; source-layout section for contributors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants