Fix incorrect API endpoint usage for course mode creation#3394
Open
Fix incorrect API endpoint usage for course mode creation#3394
Conversation
OpenAPI ChangesShow/hide ## Changes for v0.yaml:Unexpected changes? Ensure your branch is up-to-date with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are the relevant tickets?
Closes mitodl/hq#10575
Description (What does it do?)
Cloning a course run through
process_course_run_clonetriggers calls to update edX course run data and create course modes in edX. When it does this, it passes along the edX API client object that it set up to these other function calls. However, these edX APIs are in different places - the course run clone API is in Studio, the rest are in the LMS - so they end up failing. This PR fixes that by not passing along the client.How can this be tested?
You will need a working Tutor setup to test this.
Re-run a course and check the Celery logs. The course mode call should work properly.