[Bug]: AP CLI gateway health check command doesnt work
Nobody has claimed this yet.
- 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
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI), Aspect/Other (Anything else which does not match above categories)
Description
getting the following output when we use the cli
⚡ ap gateway health
Error: health check failed with status 404: 404 page not found
but when we try with the rest api it works
⚡ curl -s --max-time 3 http://localhost:9094/health
{"status":"healthy","timestamp":"2026-04-28T05:39:44Z"}
Steps to Reproduce
as mentioned above
Severity Level of the Issue
Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)
Environment Details (with versions)
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 with the ap gateway health CLI command and compare its request with the working GET /health endpoint at localhost:9094. Trace the gateway health-check path to identify why the CLI receives a 404; done means the command reports the gateway's healthy response instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 52/100