cloudfoundry / cloudfoundry/stratos
V3 API: Handle combination of service instance and user provided service instance endpoints
Open
Nobody has claimed this yet.
v3 api
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- v2 there were two types of service instances that each had their own set of create/edit/get/etc commands
- v3 there's one endpoint that caters for both types (upsi has merged into si)
- this means all the service instance lists will change, with the service instance wall the most effected
Contributor guide
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 tracing the v3 API handling for service instance lists, especially the service instance wall, and compare it with the separate v2 service-instance and user-provided service-instance flows. Done means the lists and wall consistently handle both endpoint types through the unified v3 service-instance endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100