So what's done here is that we only update plugin config props that are set to non-default values by discovery.  So anything set by the user will be maintained *unless* discovery sets that property to a non-empty, non-default value.  In which case it is assumed that the new version relies on the updated value.  This makes it important for the plugin descriptor to define default values that match what is set by the discovery impl.  If done correctly then we shouldn't see problems.  Another possibility is to allow the update to only update read-only properties (and still apply the same default-value logic) but this would limit the ability to update a change of a non-read-only property that is also set to a non-default value by discovery.

In the current use case it is critical that the DMR "path" get updated when the plugin config is updated.  Currently the auth use-case is moot as none of the Deployment resource types have auth props.