Closed arturskorupa closed 1 month ago
The prolonged Ready
state after deletion is not on our side, this is the information we get from the yaml. Our part is to handle the case when there is no resource details.
We need to disable onClick for details view, when module is also in Error
state, because when I'm adding the eventing for example, for couple seconds/minutes it is in Error
state and extension for details is not available.
Remedy UI must be more resilient, not to be broken for the time of module deletion. 404 page may be displayed but it must have a link back to the module list.
+We need to check why module's UI was deleted but the module still presented as Ready on the list (is it something wrong with module deletion process or some caching in UI?)