started_at live events for course copy and blueprint sync. - #2647
Open
JoshBothell wants to merge 1 commit into
Open
started_at live events for course copy and blueprint sync.#2647JoshBothell wants to merge 1 commit into
JoshBothell wants to merge 1 commit into
Conversation
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
1 participant
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 live event consumers to be notified when a blueprint sync or course copy (including zip imports, common cartridge, etc.) is started.
The motivation for this is so that if the consumer is trying to keep an index of content with minimal API calls, a started_at event will keep them from making calls for the flood of events caused by a course copy.
This is a bit more involved than our previous live event PRs, but I believe it is correct and useful.