feat: handlers for taxonomy xblock openedx-events

[navinkarkera]

Description

Implements handlers to catch openedx-events related to xblocks like deletion, duplication and publish. Currently these handlers just trigger related signals provided by taxonomy-connectors which do the leg work of updating xblock skills.

Private-ref: BB-6931

Dependencies:

• feat: xblock deleted and duplicated event handlers taxonomy-connector#127
• feat: adds events to handle changes in xblocks openedx-events#143

Merge checklist

• Merge all dependencies.
• Update taxonomy-connector version

[openedx-webhooks]

Thanks for the pull request, @navinkarkera! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[mphilbrick211]

@ansabgillani could you please take a look and allow tests to run?

[tecoholic]

@navinkarkera While the code is straightforward, I am wondering about the necessity of this new handler. This feels like a glue code that does the following:

                                 even handler                       event handler  
|---------------|   signal   +-------------------+  signal   +--------------------+
|openedx-events |----------->| Course Discovery  | --------->| taxonomy connector |
|---------------|            +-------------------+           +--------------------+

Is there a reason why we cannot simply add openedx-events directly as a dependency to the taxonomy connector and achieve something like this?

                                                   
                                    event handler  
|---------------|   signal   +--------------------+
|openedx-events |------------| taxonomy connector |
|---------------|            +--------------------+

[navinkarkera]

@navinkarkera While the code is straightforward, I am wondering about the necessity of this new handler. This feels like a glue code that does the following:

                                 even handler                       event handler  
|---------------|   signal   +-------------------+  signal   +--------------------+
|openedx-events |----------->| Course Discovery  | --------->| taxonomy connector |
|---------------|            +-------------------+           +--------------------+

Is there a reason why we cannot simply add openedx-events directly as a dependency to the taxonomy connector and achieve something like this?

                                                   
                                    event handler  
|---------------|   signal   +--------------------+
|openedx-events |------------| taxonomy connector |
|---------------|            +--------------------+

@tecoholic Like I mentioned in openedx/taxonomy-connector#127 (comment), openedx-events is already a dependency in course-discovery so I did not include it in taxonomy-connector.

[navinkarkera]

Closing as the signals are now directly handled in openedx/taxonomy-connector#127

[openedx-webhooks]

@navinkarkera Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.