...
[10:33:13 CST(-0600)] <dmccallum54> k
[10:34:14 CST(-0600)] <dmccallum54> i think the main thing on the SSP side is that it doesn't really ever check 'roles' in the uP groups sense… think it's always checking uP permissions, which get mapped one-to-one to spring security roles/grantedauthorities
[10:48:12 CST(-0600)] <TonyUnicon> but the roles are a collection of permissions essentially?
[10:48:21 CST(-0600)] <dmccallum54> correct
[11:16:28 CST(-0600)] <dmccallum54> js70 the work i did on avoiding N+1s for the caseload report was tracked by SSP-585 (can find the git commits there)
[11:16:58 CST(-0600)] <dmccallum54> also, i misremembered the perf integration test… it was for person lookup rather than the report itself
[11:17:21 CST(-0600)] <dmccallum54> but you can find it at PersonServiceBulkCoachLookupIntegrationTest#testLiteCoachLookupMuchFasterButPotentiallyIncomplete()
[14:19:52 CST(-0600)] <TonyUnicon> are the *.permission-set.xml files generated?
[14:37:06 CST(-0600)] <dmccallum54> as far as i know they're created by hand
[14:37:35 CST(-0600)] <dmccallum54> not to say a script wouldn't be helpful
[14:37:39 CST(-0600)] <dmccallum54> but dont think such a thing exists
[15:13:17 CST(-0600)] <TonyUnicon> my skype flaked out, gonna call on the land line
[15:55:32 CST(-0600)] <dmccallum54> to our current (phone) conversation… for tickets you think you'll finish in the current iteration, set fix version to 1.2.x and https://issues.jasig.org/browse/SSP/fixforversion/12483
[15:56:53 CST(-0600)] <dmccallum54> i also created https://issues.jasig.org/browse/SSP/fixforversion/12484 in case it turns out to be convenient to queue up work for the "next" iteration as you go