a7 GA Readiness

[shreemaan-abhishek]

Goal

Make a7 stable enough for GA by end of May and safe to recommend to users for API7 Enterprise Edition management-plane operations.

Tracking issue for the GA Readiness Handoff. Scope is management-plane validation (CLI CRUD, declarative config, correctness against real API7 EE 3.9.12), not new Phase 9 enterprise features and not data-plane traffic forwarding (that stays in the gateway repo).

Context

• PR Remove unsupported API7 resource commands #21 (remove unsupported API7 resource commands) is merged.
• Verified against the control-plane repo: stream-route IS exposed by the CP management API; plugin-config is NOT.
• Test plan: docs/ga-test-plan.md.

Sub-issues

Work is broken down into the linked sub-issues below.

Exit criteria

• Core resource commands work against real API7 EE.
• E2E covers full CRUD round-trips through the CLI.
• config sync/diff/dump/validate work with service-centered resources.
• Unsupported resources are removed or clearly blocked.
• Docs and skills only describe supported workflows.
• CI green on master.
• Release notes state supported API7 EE versions and unsupported resources.

[coderabbitai]

🔗 Related PRs

#2 - test: align E2E coverage with current EE models [merged]
#6 - test: strengthen E2E readback assertions [merged]
#7 - docs: align mTLS skill with service model [merged]
#9 - docs: migrate traffic recipes to service model [merged]
#20 - fix update commands to preserve full PUT payloads [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!