Grouper Developers Forum

[Tom Zeller <>]

Well, a use case was group deletes. I would need to use PIT to find
groups which have been deleted since some point in time. Just omitting
the whole feature in lieu of the changelog would be simpler. As of
now, we sort-of update groups which have been changed since some point
in time, as long as they haven't been deleted.

> Right, I think we let existing functionality work, but I think we don't 
> need to add more code to it...  so I would suggest allowing selecting 
> groups which have changed since a point in time, but not add support for 
> stems and members, just my opinion :)
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Tom Zeller
> Sent: Tuesday, October 18, 2011 3:04 PM
> To: Chris Hyzer
> Cc: Grouper Dev
> Subject: Re: [grouper-dev] last modified time for stems and members ?
>
>> Isnt what you are referring to what you would do if you didn't have the 
>> option to do incremental real-time provisioning?  i.e. once we have 
>> incremental real-time, then what is the use case to require finding 
>> objects which have changed in folders in the past certain amount of time?
>
> Right, if everyone is using real-time provisioning then we might not
> need to provision objects which have been changed since some point in
> time. However, for now, I would like to maintain the ability for
> ldappcng to select objects for provisioning based on the time since
> last change.
>
> So the use case would be : deployers who for whatever reason aren't
> going to use real-time provisioning upon first release.
>