Page MenuHomePhabricator

Story: User creates cohort with CentralAuth insertions
Closed, ResolvedPublic

Description

As a program manager,
I can select the checkbox labeled XYZ when uploading my cohort,
so wikimetrics will automatically add CentralAuth users’ accounts from other projects

Lable XYZ: Expand cohort to all user’s accounts across projects (via CentralAuth)

  • the only time user sees this is when uploading a cohort. No other references to CentralAuthUser are necessary.
  • The UI does not need to distinguish cohorts that include accounts taken CentralAuth
  • short form: program manager checks “expand...” when uploading cohort

Version: unspecified
Severity: enhancement
Whiteboard: u=WikimetricsUser c=Wikimetrics p=21 s=2014-10-16

Details

Reference
bz66843

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 3:25 AM
bzimport set Reference to bz66843.

74 hours
(8 hours working days for Teresa)

  • (10 hours) puppet would need to be updated to create central auth testing database in vagrant (check central-auth role in vagrant. See class role::centralauth in puppet/manifests/roles/centralauth.pp in vagrant)
    • puppet database definition has a if debug section that creates these test databases
  • (16 hours) update database configuration and scripts
    • we have get_session, get_mw_session and we would need get_ca_session that would return a centralauth session
    • scripts create local versions of the test databases (for when we're not using puppet to develop)
  • (16 hours) models to map to central auth database in labs (same access as other databases).
    • new folder wikimetrics/models/centralauth, analogous to wikimetrics/models/mediawiki
    • four tables only (the ones being used)
    • test mappings in tests/test_models/test_mappings.py
  • (14 hours) make new ways of adding central auth test data to centralauth testing db
    • simple signature: add_central_auth_users(user_names, projects)
    • currently, create_test_cohort is our primary function for inserting controlled test data into blank mediawiki test databases. For this task, you'd need to make an analogous test data creation utility method
  • (16 hours) validation would need to include an option to expand users into all matching central-auth users (make sure there are no duplicates)
  • (2 hours) user interface updated
    • Just a checkbox. Analytics team handles the redesign, because that's needed anways.