Actions
User story #2418
closed
Add some cleverness in the management of accepted/pending/removed nodes
Status:
Rejected
Priority:
3
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
When we accept/remove nodes, or when one inventory is received, a lot of informations are shuffled around branches. For now, we may have a lot of duplication, and no detection of duplicates over branches
We should :- Modify the accept inventory service to look for deleted inventories, and restore a matching deleted inventory
- Have some clever part that would solve possible conflict (for instance, if the inventory is not completely the same as before)
- Figure if we should also save the inclusion in static groups (with the same issue has previous point, if the node is really deleted or just a mistake)
It is a consequence of #2094
Updated by Jonathan CLARKE almost 12 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by François ARMAND about 11 years ago
- Assignee deleted (
François ARMAND)
Updated by Nicolas CHARLES almost 4 years ago
- Status changed from New to Rejected
rejecting: it's done in a different way, we do search in other branches
Actions