Add support for migrations by URL #40
Merged
Conversation
This file contains 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
This allows for content migrations to have a URL to import rather than a file. It also fixes the option so that we don't use the user ID to perform a import to a group or account. This does change the API for content migrations, but it makes it clear that people shouldn't continue to use the API as it was.
mpellicer
approved these changes
Oct 5, 2021
There was a problem hiding this comment.
Makes sense according to the API:
https://canvas.instructure.com/doc/api/content_migrations.html#method.content_migrations.create
Supports users, groups, accounts and courses.
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.
This allows for content migrations to have a URL to import rather than a file. It also fixes the option so that we don't use the user ID to perform a import to a group or account.
This does change the API for content migrations, but it makes it clear that people shouldn't continue to use the API as it was.