cloudfoundry / cloudfoundry/stratos
Fetch service brokers a better way
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- we show details of a service's broker in the marketplace
- some cf's give a 404 when trying to fetch the broker inline or directly
- this results in 9 (/page size) failed requests
- need a better way to handle this
Option 1
- i noticed that calls to list service brokers succeed (though are empty)
- although less efficient, we could fetch this list to access service brokers, or not if missing, rather than using the standard entity service way
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 how the marketplace fetches service-broker details, including the inline or direct request and the list-service-brokers path described in the issue. Compare the behavior when a broker is missing and verify that marketplace pages no longer generate the repeated 404 requests while still showing available broker details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- api, cloud, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100