GSH changelog consumer

Changelog consumers fill a gap between hooks, rules, and provisioners. They are able to act on a variety of change activity, not immediate like hooks, but more flexible than provisioners.

Like those other features, creating a changelog consumer requires custom Java programming. This makes it an undesirable solution for institutions that want to stay away from required Java expertise for creation and ongoing support.

Ideas:

• Framework will set variables for List<ChangeLogEntry> changeLogEntryList and ChangeLogProcessorMetadata changeLogProcessorMetadata, which are the sames parameters as would be passed to processChangeLogEntries()
• Should set up a Logger variable, for optional logging
• Set up a debugMap variable, but don't output anything if it isn't used and stays empty
• Properties
  • changeLog.consumer.myGshScript_1.class = edu.internet2.middleware.grouper.changeLog.consumer.GshChangeLogConsumer
  • changeLog.consumer.myGshScript_1.name = myScript_1
  • changeLog.consumer.myGshScript_1.script = //
  • changeLog.consumer.myGshScript_1.retryOnError = false
• Like gsh templates, the script should go into a configuration variable. It could be created in grouper-loader.properties if the lines are escaped, but it's going to be easier to paste it in via the UI