[Task]: Support Gateway Versions in Platform API
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
As there are new gateways released (minor/major releases with new features) the platform api needs to keep track of which version it belongs to.
This would help populating correct setup URLs, correct configurations in the portals as platform api acts as backend to it.
In addition this would help maintaining backward compatibility.
Key Decisions to Make:
- How granular version we expect to keep.
- Should the verision be updated as a explicit manual task, or else should platform api depend on gateway controller to notify if there is a version change.
- Can a gateway upgraded to its major version without creating a new gateway.
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 implementation files, tests, or entry points are named. Start by reviewing the platform API and its gateway controller integration, then resolve the required version granularity, update mechanism, and major-upgrade behavior. Done means the platform API tracks gateway versions to support correct setup URLs, configurations, and backward compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100