Support Main and Sandbox Endpoints in API YAML
Open
Nobody has claimed this yet.
Type/Task
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
Gateway Config
gateway_main_host: "*.prod.wso2.com"
gateway_sandbox_host: "*.sand.wso2.com"
Simplest API YAML with just the main endpoint.
version: api-platform.wso2.com/v1
kind: http/rest
metadata:
name: Weather-API
version: v1.0
spec:
context: /weather
upstream:
main:
url: http://prod-backend:5000/api/v2
gatewayHost: # optional gateway host
main: apis.apis.prod.wso2.com
operations:
- method: GET
path: /{country_code}/{city}
With sandbox endpoint
version: api-platform.wso2.com/v1
kind: http/rest
metadata:
name: Weather-API
version: v1.0
spec:
context: /weather
upstream:
main:
url: http://prod-backend:5000/api/v2
sandbox:
url: http://sandbox-backend:5000/api/v2
gatewayHost: # optional gateway host
main: apis.apis.prod.wso2.com
sandbox: apis.sand.wso2.com
operations:
- method: GET
path: /{country_code}/{city}
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 locating the API YAML parsing or validation entry point and any existing handling for upstream and gatewayHost. Compare the main-only and sandbox examples; done means both endpoint forms are accepted consistently, with coverage for the configurations shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100