Redirect from cmdb_ci_spkg and cmdb_software_instance to cmdb_sam_sw_install

[poyntzj]

I know that installing SAM has changed discovery so that when it detects software it now updates the cmdb_sam_sw_install table

Does anyone know what the actual mechanism is to make this change ?

I have a client who for various reasons need the original tables (cmdb_ci_spkg and cmdb_software_instance) updating for the next little while before changing - this is due to a plugin.

Not seen anything obvious, but need this for now 😞

[poyntzj]

Hi RP

I am aware of how it works and the mechanism involved.  The issue I have is that my client still need to use the CMDB tables and not the SAM ones for the next little while, but SAM is installed.

As with my other reply, I am sure the code that does this use SAM/use CMDB is in SNC hidden code.

I can work this via using the installed software pattern instead of using the probe/sensor