cloudfoundry / cloudfoundry/stratos

Wire in `last operation` to service instance info & actions

Open
#3,120 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

  • last operation info in SI cards, rows, summaries, etc
  • operations include create, update, delete
  • states include in progress, succeeded, failed
  • Don't allow actions depending on state
    • Cannot bind application to service if it create/delete is in progress or failed
    • Where ever we do this we must provide a way to easily refresh this state
  • see https://apidocs.cloudfoundry.org/231/service_instances/list_all_service_instances.html for more info
  • See #3090 for reason

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 by tracing service instance cards, rows, summaries, and their action handlers to identify where operation state is displayed and checked. Read the linked Cloud Foundry service-instances API documentation for the available last-operation fields. Done means create, update, and delete states are shown and actions are blocked or refreshable when an operation is in progress or failed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.