I assume you’re doing it as a configsource because you want to save the output of the script as a blob of text, readable from LM? Have you considered containerizing your python script and pushing the logs to LM Logs via the API?
My main reasons (probably all bad? :)) would be:
- I want the daily results shown in the text so that people can make note of when an action happened
- I am in a weird position where I dont have easy access to any collectors where the python would run. When I “inherited” the “portal admin” dutues all of a sudden, I inherited a bunch of python scripts my predecessor wrote that just run on a windows collector. But I dont really have easy access to that collector, so I ported all of them away from external python (there were only a few). It is super tedious to have to get permission to maintain the code each time. So I wanted it all in-platform for LM.
- I generally want the code to be native groovy or powershell anyway, because in case I get hit by a bus or something, I want someone else coming in to look at the config source to be able to literally see the code there in the LM platform.
- I got in the (bad?) habit of doing all our platform scripts as config sources, all running against our portal resource object, so habit I suppose.
As for LM Logs, I’ve never had need to use them. I think there are some basic log-related functionalities I’ve never needed to use, and I seem to recall that the fancy LM Logs thing is a pay-for feature. Not sure.
Expert