You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're attempting to automate roster population in Autolab for our courses, but we've encountered an issue: there's no way to use the API to create users. Initially, we were POSTing to /api/v1/courses/{course_name}/course_user_data, but this approach fails if the user doesn't already exist, as it won't create a non-existent user the way the user model's function, self.roster_create, does when rosters are uploaded via the GUI.
Therefore, we either need an endpoint for user management (/api/v1/user_controller) capable of more than just retrieval - specifically, one that can create, update, and destroy users. Alternatively, we could modify /api/v1/courses/{course_name}/course_user_data to call the user's self.roster_create function, rather than merely reporting that a user doesn't exist.
The text was updated successfully, but these errors were encountered:
Thanks for this feature request and we'll take a look into it!
As a workaround in the meantime, if your script has access to the Autolab instance, you could consider using the rake task rake admin:create_user[email,password,first_name,last_name] to create missing users programmatically
We're attempting to automate roster population in Autolab for our courses, but we've encountered an issue: there's no way to use the API to create users. Initially, we were POSTing to /api/v1/courses/{course_name}/course_user_data, but this approach fails if the user doesn't already exist, as it won't create a non-existent user the way the user model's function, self.roster_create, does when rosters are uploaded via the GUI.
Therefore, we either need an endpoint for user management (/api/v1/user_controller) capable of more than just retrieval - specifically, one that can create, update, and destroy users. Alternatively, we could modify /api/v1/courses/{course_name}/course_user_data to call the user's self.roster_create function, rather than merely reporting that a user doesn't exist.
The text was updated successfully, but these errors were encountered: