Weird active discovery on Microsoft_SQLServer_Databases?
I'm in the process of updating all my modules to the new groovy4 versions, and I kinda saved the big impact ones for last. I'm literally about to update the last one, Microsoft_SQLServer_Databases, but when doing a test prior to the update, the new version gives back too many instances found than it should.
It always seems, no matter what server I test with my appliesTo and my ActiveDiscovery, its usually the first 4 duplicated onto the end.
Version 2.13.0 Gives this list, as an example:
MSSQLSERVER/master
MSSQLSERVER/tempdb
MSSQLSERVER/model
MSSQLSERVER/msdb
MSSQLSERVER/QRST
MSSQLSERVER/UVWX
MSSQLSERVER/ABCD
MSSQLSERVER/EFGH
MSSQLSERVER/IJKL
MSSQLSERVER/MNOP
MSSQLSERVER/QRST
MSSQLSERVER/UVWX
MSSQLSERVER/YYZ
Version 2.16.0 (latest) gives this result:
MSSQLSERVER/master
MSSQLSERVER/tempdb
MSSQLSERVER/model
MSSQLSERVER/msdb
MSSQLSERVER/QRST
MSSQLSERVER/UVWX
MSSQLSERVER/ABCD
MSSQLSERVER/EFGH
MSSQLSERVER/IJKL
MSSQLSERVER/MNOP
MSSQLSERVER/QRST
MSSQLSERVER/UVWX
MSSQLSERVER/YYZ
MSSQLSERVER/master
MSSQLSERVER/tempdb
MSSQLSERVER/model
MSSQLSERVER/msdb
I have all the dependencies mentioned under Technical Notes up to date. And it seems that every time I test the code I get these instance duplicates.
BTW the way I'm testing is I go to our test portal, update to latest, export as json, rename the file and the places inside the file to give it a new name, strip out the publish/identity hash section, change the appliesTo to false() and import back into the test environment. Then if it looks good, I import into prod, which I have done, but its completely a differently named version of the update with an empty appliesTo. Then I can hit edit and temporarily change the appliesTo without saving, and then test the active discovery. So I can see exactly what it will do.
Has anyone else experienced any weirdness like this? Is this common?
Thanks!