Visually deleted component actually runs in the env until the next deployment (no ui indication)
Bug #1576180 reported by
Valerii Kovalchuk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
In the environment components view, when we delete the deployed component, we should not hide it from the components list, but just change its status to something like "Marked for deletion". It will make clear that component is still running in the environment until the next deployment.
Changed in murano: | |
status: | New → Confirmed |
tags: | added: dashboard |
Changed in murano: | |
milestone: | newton-1 → newton-2 |
Changed in murano: | |
milestone: | newton-2 → newton-3 |
Changed in murano: | |
milestone: | newton-3 → newton-rc1 |
Changed in murano: | |
milestone: | newton-rc1 → newton-rc2 |
Changed in murano: | |
milestone: | newton-rc2 → ocata-1 |
Changed in murano: | |
milestone: | 3.1.0 → pike-2 |
Changed in murano: | |
milestone: | pike-2 → pike-rc1 |
To post a comment you must log in.
I like this kind of UI logic. Sounds like a good idea to me, let's align it with the angularization work we're doing with this bp https:/ /blueprints. launchpad. net/murano/ +spec/switch- to-angular