[go: up one dir, main page]
Skip to content

Design Document: Add notes about Failed, Error and Unknown states

MR: Pending

Description

The following discussion from !163093 (merged) should be addressed:

  • @mvanremmerden started a discussion: (+9 comments)

    @vtak @cwoolley-gitlab One of the changes in this MR is that I tried to ensure that there is always only one state visible for the user and that we don't have two states visible at the same time (e.g. "Running" in the badge left and "Stopping" in the button tooltip on the right side).

    Over the last days @ealcantara had a look at the code for actualState and desiredState and tried to figure out how in this new design each combination should be represented, and what actions should be available. We created a new storybook page so that all combinations can quickly be seen:

    image.png

    A few questions now for both of you:

    • Are there any constraints in the backend for what combinations should not be possible between actualState and desiredState?
    • Should all actualState: error combinations have "Error" as state indicator in the badge?
    • Should there be any actions (Start, Stop, Restart, Terminate) visible in the dropdown on the right side for actualState: error and` actualState: unknown`?

Acceptance Criteria

TODO: Fill out (required)

  • [Describe what must be achieved to complete this issue.]
  • [Describe another requirement needed to complete this issue.]
  • [Add additional acceptance criteria as needed.]

Technical Requirements

TODO: Fill out or delete (optional) [If applicable, please list out any technical requirements for this feature/enhancement.]

Design Requirements

TODO: Fill out or delete (optional) [If applicable, please provide a link to the design specifications for this feature/enhancement.]

Impact Assessment

TODO: Fill out or delete (optional) [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]

User Story

TODO: Fill out or delete (optional) [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]