Restrict desired inventory updates and removal based on resource tags

Current Behavior

The Limit to Resource Tag setting controls only where a component process executes. When a resource does not match the configured resource tag, the component is shown as Not Mapped and the component process is not executed on that resource. This setting does not limit desired inventory updates. The associated inventory changes are still evaluated, and inventory is managed according to normal inventory behavior, whether or not the component process is mapped to or executed on the resource. For example, an Uninstall Jazz.JTS step that is Not Mapped on an environment still affects the desired inventory of Jazz.JTS there. IBM Support confirmed that this is expected and applies to other steps that affect inventory as well.

Challenge

The "resource tag" sets the execution scope of the process but not the scope of desired inventory management. A component process that never runs on a resource can still remove its desired inventory. This is unexpected, hard to detect and hard to troubleshoot, and it can leave the desired inventory out of sync with what is actually installed.

Request

Please restrict desired inventory updates and removal based on resource tags, so that when a component is Not Mapped because of the Limit to Resource Tag setting, its desired inventory is not updated or removed.