Discovery Pattern: comment out code

[Diana Cunha]

Hello everyone,

I'm facing an issue with Discovery patterns in a client environment.

The client uses the "Linux Server" Discovery Pattern, which includes a nested pattern called "Linux - Storage". The client does not want disks to be discovered, created, or related to other CIs when Discovery runs. To achieve this, I inactivated the "Linux - Storage" pattern and also removed it from the parent pattern.

This approach seems to be working as expected — disks are no longer being created, and some existing ones are being removed based on the deletion strategies configured.

However, there is now a new issue: the "UNIX Cluster - Linux Pacemaker Cluster" extension is failing at the initial steps of Discovery. This extension was working properly before "Linux - Storage" was inactivated, and it is required because the client wants to retain those Cluster-related CIs.

My questions:

1. Is the failure of the Pacemaker Cluster extension related to the inactivation of "Linux - Storage"?

2. Is it better to comment out only the specific sections in "Linux - Storage" responsible for creating disks, rather than inactivating the entire pattern?

3. Would modifying "Linux - Storage" cause issues with upgrades or stop ServiceNow support in this matter?

Any advice or best practices would be appreciated.

Thanks in advance!