[Self hosted GW] Deployment failed with a error log , but no any information to UI
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/Management (Management API or Management Portal UI)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
Steps to Reproduce
- Create an API
- Add an
add headerpolicy and set a random string as the key (ie:api key) and save changes - Go to the deploy page and deploy the API
API deploy without any error. But when checking the gateway logs, there are few error logs (See the attachment above). Invoke the API works if there are any previously deployed APIs available and invoke to that endpoint.
Severity Level of the Issue
Severity/Blocker (Core functionality is broken and consumer is blocked. Need immediate 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
No files, tests, or entry points are named in the report. Reproduce the deployment after adding an add-header policy, compare the gateway error logs with the deployment page, and trace the existing deployment status flow. Done means deployment failures and their available error details are surfaced in the UI while successful deployments remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100