cloudfoundry / cloudfoundry/stratos
Update bind existing service instance to application process
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- currently binding an existing service instance to an application process is confusing
- the decision to either create a new instance or bind to existing one is made right at the end of the flow
- this late choice is enough to put of user of going through flow
- the visibility of the choice is also sometimes shown, sometimes not (given existence of applicable service). We might want to reconsider this, though only after changes above
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 application-process binding flow described in the issue and identify where the choice between creating a service instance and binding an existing one is currently made. The first change should make that choice earlier and easier to understand; consider the inconsistent visibility of the choice only after that behavior is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100