-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exposing More Autolab Functionality as an API #217
Comments
hi @namanbharadwaj, this sounds cool. What would be the example use case for "reload config"? |
@icanberk 210 has some build & testing infrastructure for labs, and I would like to be able to integrate scripts to install + update the lab configuration automatically, based on a local config, rather than TAs having to do it manually. I'll start looking into what changes this feature will entail. |
Development of an Autolab API is currently underway (#850). Right now the focus is on the student side, allowing auto retrieval of courses, assessments, and handout/writeup, and performing submissions. Once the framework is completed, we will be looking into how we can add endpoints to allow instructor/CA functionality through the API. |
I am interested in being able to hit the assessment "reload config" endpoint remotely via a
curl
. This would involve creating some concept of a course "secret key" for authentication (passed to Autolab with every request over SSL; probably want the ability to invalidate and generate new secrets), but seems to be a reasonable project.I would be willing to work on this; I just wanted to check whether you'd be willing to merge in a change like this. I'm on the 210 course staff, and am interested in automating more of the 210-specific lab management workflow; are there other endpoints that might be useful to hit remotely?
The text was updated successfully, but these errors were encountered: