cloudfoundry / cloudfoundry/stratos
Improve error handling when creating cf entities
Open
Nobody has claimed this yet.
bug
P2
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- We create cf entities in many places (route, org, space, app, etc)
- At the moment we don't, or show vague, error messages
- In a lot of cases we could probably just show the 'description' from the cf response (need to either get this from changing requests to passthrough or improving jetstream response...)
A few specific instances...
Create Route (in create app modal)
- Need to show specific error message from description
Create App - If either create app, route or bind(?) fail we don't get any feedback.
- Feedback is specifically important for route creation (for instance
The host is taken: <x>")
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 entity creation from the create app modal and the route, org, space, and app flows. Inspect how create, bind, and Jetstream responses are currently surfaced, including whether passthrough is available. Done means failures show the Cloud Foundry description, including route errors, and create-app failures provide feedback to the user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100