Description of problem: Currently, the path for removing an entity (VM / Template) is the same path as removing an entity which resides on an export domain. So before removing the entity, we should decide whether that entity is an unregistered entity or not. In order to decide whether the entity is unregistered or not a query sent to the backend, to avoid that query we should split the path for unregistered entities or have a specific signature for each flow in the 'Remove' interface Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Eyal, changing the path is basically breaking the current API behavior, something we should not do, what do you suggest?
So I think it will be better to go on the second option to overload the 'remove' interface so it will distinct between unregistered entity remove and exported VM removal.
This bug/RFE is more than 2 years old and it didn't get enough attention so far, therefore it can be closed. Please re-open if this RFE is needed.