When updating plugins that make changes to the plugin defined drift definitions there are a few issues. 1) If there are user-defined templates they can get removed accidentally 2) If there are attached definitions to the updated templates they can cause FK constraint issues. 3) There is no protection against directory update on an existing template. This can cause issues for pinned templates.
master commit eb021c14ddf1f673a500e237c161bf480fc74bb6 release_jon3.x commit 89cb974ef54fd2dcf79a74b6ba466d85c831e657 TEST NOTE: Testing drift meta-data changes is maybe a little difficult as the easiest way to do this is to build updated versions of the plugins and then deploy them to your server. Still, it's doable by unzipping the plugin, tweaking the rhq-plugin.xml, rezipping and then dropping into the rhqserverhome/plugins dir. See: http://rhq-project.org/display/RHQ/Drift+Management#DriftManagement-Howtohandlepluginupdatestothedrifttemplates For expected plugin update behavior.
this is not really something customers do