Invalid 'Gateway' URL when publishing an API to the developer portal
Open
Nobody has claimed this yet.
Area/DeveloperPortal
Priority/Highest
Severity/Major
Type/Bug
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
When I try to add an API to the developer portal, it asks me for a "Gateway" url. There are two issues here.
- The default value shown is the URL of the back-end of the API. The default value should be the value of the Gateway's endpoint (8080).
- At this time, the notion of Gateway should not be presented. What is important is the access URL of the API. In most practical/real-world scenarios this URL/DNS would be of that of the Load Balancer fronting the Gateway. So please remove the word Gateway and just say Endpoints -> Main API endpoint.
Steps to Reproduce
See above.
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 in the developer portal form used when adding an API, where the Gateway URL is requested. Verify the default uses the Gateway endpoint on port 8080 and that the field is presented as the main API endpoint rather than Gateway; the issue is done when both requested UI behaviors are reflected.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100