Expert
I totally get your frustration. It's what i've been dealing with trying to use the common configsources where the logic is spread over a dozen property sources too.
Lots to unpack here so let me restate to understand the problem: you have a configsource. The target data changes often. You have a config check alerting on diff and you have some exclusions in that check that use regex. That regex matches the line that changes, so you shouldn't see alerts. All of this is happening as expected. However, you are expecting to see a new version registered in LM, but you're not.
Is that it?
ExpertOne extra step at the end.
I made a clone of the config check that, instead of reaching out to the host to grab the config, it prints out the top few lines of a config I grabbed once, hard coded, but with ONE character on the line in question altered, at random 0-9, on the line of concern. Because I dont want to wait on the REAL config source to happen change once every 2 weeks to test it.
And while in test mode for the config source, I see the line changing that one character every time I hit play to test, once I apply this config source to my ONE applies-to target, it runs the random thing and give me my "fake config" but it NEVER EVER re-runs the script, seemingly, such that my line of concern changes.
Its always giving me the original run.
The code is 3 lines:
def myNum = Math.abs(new Random().nextInt() % 10).toString();
print("#config-version=FGT61F-7.0.14-FW-build0601-240206:opmode=1:vdom=0:user=lm\n#conf_file_ver=542255083128888" + myNum + "\n#buildno=0601\n#global_vdom=1\nconfig system global");
return 0
it runs the random thing and give me my "fake config" but it NEVER EVER re-runs the script
I think this may be a bug, but LM may say working as designed. Since the line is ignored, I'm not sure how LM is supposed to handle a change in an ignored line. Obviously it shouldn't alert, and it isn't. But should it register a new version? Maybe, maybe not. One reason i can think of to not register a new version is that if the ignored line contained the current time, it would change every time it was collected. If LM registered a new version for every change, including an ignored line with the time on it, you'd have a new version every poll cycle. For this reason, I think LM may consider this "working as designed".
The script may be running, not using a cache or anything else. Your "test script" executions have intimated as much. It comes down to LM's decision whether or not to consider the difference sufficient enough to merit registering a new version in the UI.
Clarify one more thing though: your screenshots of the diff view above show the same timestamp on both sides. Obviously that's a UI inconvenience that you can show the same thing on both sides, or that the same thing comes up on both sides by default. I'm not sure i completely understand: are you saying it's registering a new version when there truly is a change, but the new version has the same content as the old version?
