cloudfoundry / cloudfoundry/stratos

App Summary Actions: Enable when app is stopped + pending

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

Nobody has claimed this yet.

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

Description

  • App state can be 'STOPPED' 'PENDING' when..
    • App has been created using deploy stepper with the 'do not start' option checked
    • App has been created using deploy stepper and will subsequently become 'STARTED' 'STAGED'
  • When in the stopped pending state we show 'Offline while Updating' and disable the start,restage, etc actions
  • For the first app state above we're then blocked from actually starting the app
  • However for the second app state above they should be blocked to avoid starting an app that's staging
  • Lesser of two evils... enable the app actions when in stopped pending state
  • Should first check what actions do when app is staging

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 the App Summary action handling for STOPPED and PENDING states, then compare it with the behavior while an app is staging. Done means actions are enabled for the stopped-pending case created with “do not start” while remaining safe for apps that are progressing toward STARTED/STAGED.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.