Description of problem:
Currently we don't support resource name change. When plugin writer decides to rename his resource type, server hanldes it wrong way - it understands it as resource type deletion and addition - so at first it uninventories all resources of the missing type and later on resources of new type get discovered. all metrics and history data are lost.
We need to support type name change. It would be enought if we introduce attribute 'originalName' in plugin descriptor. On server, when deploying new version of plugin .. this attribute can be used to match existing resource types.
Version-Release number of selected component (if applicable):
You may need to make that 'originalName' attribute allow for several names, so that you can change it more than once ans successfully upgrade from different versions. I'm not sure but maybe something like: