07-12-2016 07:47 AM
I'd like to set up triggered jobs for a number of policy rules but the script these triggers will run is pretty generic. I'd like to avoid having to maintain a seperate script for every triggered job. Is there a way to tell the script which rule triggered the job? I expect I'll be triggering a Perl script.
Solved! Go to Solution.
07-13-2016 06:13 AM
Probably John Belamaric will answer if that job detail is available via the API.
But for similar scripts triggered via policy violations, I've always had the script check the same rules via CLI. That prevents a script from modifying a config that is already compliant. And it can be safely run manually without relying on correct rules and policies.
07-15-2016 06:58 AM