Background
The latest API7 EE versions have removed the service template APIs, including the control-plane endpoints currently used by a7 service-template, such as:
/api/services/template
/api/services/template/{id}
/api/services/publish
In PR #16, E2E was adjusted to skip service-template tests when the current API7 EE environment returns 404 HTML or resource not found. That keeps CI green, but it is only a compatibility guard. The CLI still exposes service-template commands even though the backing API is no longer available in current API7 EE.
Problem
Keeping a7 service-template as a normal command can mislead users into expecting the feature to work against supported API7 EE versions.
Current affected areas:
pkg/cmd/service-template/*
docs/user-guide/service-template.md
- skills or recipes that reference
a7 service-template
- E2E tests in
test/e2e/service_template_test.go
- command discovery/help output
Proposed Follow-Up
Decide how to remove or deprecate service-template support.
Suggested options:
- Remove the
service-template command group entirely if no supported API7 EE version exposes these APIs.
- Or keep a compatibility command that fails fast with a clear message explaining that service templates are no longer supported by API7 EE.
- Remove or update docs and skills that teach users to use service templates.
- Remove service-template E2E CRUD coverage, or keep only a lightweight compatibility/error-message test.
- Update any roadmap or API spec docs that still describe service-template as available.
Acceptance Criteria
- Users are not guided toward
a7 service-template as a working API7 EE workflow.
- CLI behavior is explicit: removed command, hidden command, or clear deprecation/unsupported error.
- Docs and skills no longer present service-template as a supported current API7 EE resource.
- E2E no longer contains full CRUD coverage for APIs that no longer exist.
Background
The latest API7 EE versions have removed the service template APIs, including the control-plane endpoints currently used by
a7 service-template, such as:/api/services/template/api/services/template/{id}/api/services/publishIn PR #16, E2E was adjusted to skip service-template tests when the current API7 EE environment returns 404 HTML or
resource not found. That keeps CI green, but it is only a compatibility guard. The CLI still exposes service-template commands even though the backing API is no longer available in current API7 EE.Problem
Keeping
a7 service-templateas a normal command can mislead users into expecting the feature to work against supported API7 EE versions.Current affected areas:
pkg/cmd/service-template/*docs/user-guide/service-template.mda7 service-templatetest/e2e/service_template_test.goProposed Follow-Up
Decide how to remove or deprecate service-template support.
Suggested options:
service-templatecommand group entirely if no supported API7 EE version exposes these APIs.Acceptance Criteria
a7 service-templateas a working API7 EE workflow.