Grouper Users - Open Discussion List

["Bee-Lindgren, Bert" <>]

FWIW, I agree with the broader scope of the issue. 

On Apr 17, 2019, at 7:10 AM, Black, Carey M. <> wrote:

Jeffrey,

 

I actually think this is a more general “Grouper project” scoped issue.

 

Exact same thing happens for Change Log Consumers (CLC’s).

REF: https://lists.internet2.edu/sympa/arc/grouper-users/2019-01/msg00056.html

 

 

I expect the general design currently is:

                “add all stuff from the config files”.

                And the project does not “disable stuff it did not find in the config files.

                                It does not even “warn” about stuff it did not find in the config files. Which might be a half way step to avoid removing/breaking things as a result of a single misconfigured file.

 

In short, the full life cycle for add/update/remove does not appear to be implemented. Resulting in a “hotel California” condition. (“You can check in any time you like. But you can never leave.“)

 

--

Carey Matthew

 

From: <> On Behalf Of Crawford, Jeffrey
Sent: Tuesday, April 16, 2019 3:06 PM
To: Grouper Users <>
Subject: [grouper-users] PSP_NG Full Sync config deactivation issue

 

This one is probably for Bert

 

I put in a full sync config a while ago following the instructions at:

https://spaces.at.internet2.edu/display/Grouper/Grouper+Provisioning%3A+PSPNG#GrouperProvisioning:PSPNG-FullSYNCProvisioning

 

This was however only to test something, and I later removed the otherJob.XXX_full entries. However I looks like they got saved in the repo, so I had to add them back in and set the quartzCron to something like 59 59 23 31 12 ? 2099 to effectively disable the job. I appears that taking out the config item in grouper-loader.properties doesn’t clean out the actual job from GROUPER_QZ_CRON_TRIGGERS (And Possibly others).

 

Thanks

Jeffrey C.