cloudfoundry / cloudfoundry/stratos

Create Service Instance Stepper: Bind to app fails for async SI's

Open
#4,161 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug community
Dominant language
TypeScript
Stars
267
Forks
137
Avg merge
5h 14m
Merged PRs (30d)
77

Description

  • when creating a SI we specify accepts_incomplete, which means for async SI creation CF returns SI entity as if it were created
  • then, if bind to app is specified, we attempt and fail to bind to it
  • before binding we should check last_operation, and act differently if create is still in progress
  • we could do one of...
    • (low bar) show message that we can't bind just yet
    • poll SI and wait until service is created before binding (what would we do if this takes a looong time?
  • Can test async SI creation using overview-broker

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Create Service Instance stepper's bind-to-app flow and reproduce asynchronous service instance creation using overview-broker. Read how last_operation is handled before binding, then determine whether the accepted behavior is to show a message or wait for creation to finish; done requires the selected behavior to avoid attempting an early bind.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cloud, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.