[Improvement]: CLI doesn't support LLMProxy LLMProvider related list/removal operations
Open
Nobody has claimed this yet.
Aspect/UI
Type/Improvement
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
CLI
Please select the aspect the issue is related to
Aspect/UI (Frontend layouts, components, styling)
Suggested Improvement
Currently we can add/update LLMProviders/Proxies via CLI using
ap gateway apply -f <filename.yaml>
But we don't any listing operations specific to them. So if anyone wants to list existing, remove any of them, they need to directly talk to REST API.
Related Issues
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the CLI path for ap gateway apply -f <filename.yaml> and identify how LLMProviders and LLMProxies are represented. Review the corresponding REST operations mentioned in the issue, then add CLI support for listing and removing these resources; done means both operations work without direct REST API calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100