Visually deleted component actually runs in the env until the next deployment (no ui indication)

[Valerii Kovalchuk]

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.

[Kirill Zaitsev (kzaitsev)]

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

[Stan Lagun (slagun)]

The fact that the resources are not released just by the fact that you deleted something without environment redeployment is not a bug but expected behavior. The problem that you don't see what is going to be deleted does exist. However it is much bigger than that. It goes down to that you cannot see changes history. The same way you don't see what components were just added and never beed deployed or what properties have changed (if we have editing which is also related to this)

[Kirill Zaitsev (kzaitsev)]

I suggest to add a red/yellow visible banner, that says, that you need to press 'Deploy' to apply changes