Why is the plugin config change only detected upon version change?
I can picture a scenario when an outside change affected the resource in a such a way that it is being connected to differently, yet version remains the same. Today (and after your change) we merely mark such resource as down, leaving the user in the dark as to what might have happened. If we reported plugin config change (and could alert on it), the resource would remain "active" and the user could see a history entry in the plugin config describing the change. They could also receive an alert about the fact.