Support for Kibana APIs

[JoshMock]

Goal

Add Kibana API support to the CLI, allowing users to interact with Kibana endpoints alongside Elasticsearch and Cloud APIs.

Implementation Plan

1. Manually implement a couple of representative Kibana APIs as proof-of-concept
2. Add code generator to elastic/elastic-client-generator-js to generate Kibana API commands
3. Import all generated Kibana API code into elastic/cli

This follows the same pattern as Cloud API support (#49) and Serverless API support (#51).

Specification

The Kibana API spec is available at: https://www.elastic.co/docs/api/doc/serverless.json

[github-actions]

tl;dr: #72 should be treated as an umbrella, with Lens support as the first concrete deliverable (revive the closed draft work from #43), then add Kibana OAS discoverability to scale API coverage.

Recommendation

Implement Kibana API support in phases:

1. Phase 1 (high-confidence, concrete): add elastic kb lens (list/get/create/delete/schema) by reapplying and updating the work from closed draft PR #43.
2. Phase 2 (broader surface): add elastic kb oas discovery commands (list/get) tied to #46 so future API expansion is easier and less manual.

This balances immediate value with a path toward wider Kibana API coverage.

Findings

• #72 has only a title ("Support for Kibana APIs") and no body/comments yet, so scope is currently broad and underspecified.
• Current typed Kibana command surface is limited to dashboard + task-manager (+ raw fallback):
  • cmd/es.go:10-17 (kb root)
  • cmd/kb_dashboard.go:97-102
  • cmd/kb_task_manager.go:32-33
  • cmd/api.go:146-150 (kb raw)
• Kibana docs also list only task-manager and dashboard command groups:
  • docs/kb.md:7-8
• There is no Lens command/client code in main; only a feature flag override mention:
  • tests/functional/feature_flag_overrides.yml:2
• Related issue/PR history indicates strong prior art:
  • #42 (open) requested Lens CRUD+schema and has member follow-up to implement with functional tests.
  • #43 (closed, draft, unmerged) already contains a Lens implementation attempt (files changed include cmd/kb_lens.go, cmd/kb_lens_format.go, cmd/kb_lens_test.go, internal/client/kibana.go, docs/tests).
  • #46 (open) discusses making Kibana OAS discoverable, including runtime-vs-generated-command tradeoffs.

Verification

I ran focused checks in this workspace:

$ go test ./cmd ./internal/client
ok  	github.com/elastic/cli/cmd	0.040s
ok  	github.com/elastic/cli/internal/client	0.005s

$ go run ./cmd/elastic kb --help
Available Commands:
  dashboard    Dashboard operations
  raw          Make a raw HTTP request
  task-manager Task manager operations

$ grep -RInE 'lens|/api/lens' cmd internal docs README.md tests
tests/functional/feature_flag_overrides.yml:2:  lens.apiFormat: true

Detailed Action Plan

1. Define Support for Kibana APIs #72 scope as phased umbrella and explicitly link to #42 (Lens) and #46 (OAS discoverability).
2. Rebase/recreate PR feat(kb): add Lens visualization commands #43 as Phase 1 against current main:
   • Add/restore cmd/kb_lens.go, cmd/kb_lens_format.go, cmd/kb_lens_test.go
   • Extend internal/client/kibana.go with Lens endpoints (/api/lens, /api/lens/search, /api/lens/{id})
   • Update docs (docs/kb.md, README.md)
   • Keep/refresh functional coverage in tests/functional/functional_test.go
3. Align Lens command UX with existing dashboard patterns from cmd/kb_dashboard.go (subcommand structure, schema, output formatting).
4. Add Phase 2 OAS discoverability command group (e.g., cmd/kb_oas.go) and wire under kb, leveraging existing Kibana client/request patterns in internal/client/kibana.go and cmd/api.go.
5. Decide runtime dynamic commands vs generated static commands in #46 before attempting full API-surface automation; keep kb raw as fallback throughout.

Related Items

Type	Link	Relevance
Issue	#72	Umbrella request for Kibana API support
Issue	#42	Existing Lens API support request
PR	#43	Unmerged draft with Lens implementation candidate
Issue	#46	OAS discoverability discussion for scalable Kibana API support
Issue	#34	Completed precedent for schema-oriented Kibana command expansion
File	cmd/kb_dashboard.go:97-102	Existing kb typed subcommand wiring pattern
File	cmd/api.go:146-150	Existing kb raw fallback path
File	internal/client/kibana.go:257-337	Existing Kibana typed API methods extension area
File	docs/kb.md:7-8	Current documented Kibana command scope

---

What is this? | From workflow: Issue Triage

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.