feat: use event producer config

[navinkarkera]

Description

Replace openedx_event signal handlers with new producer config to push to event bus.

Supporting information

• Depends on feat: enable producing to event bus via settings openedx-events#249

Testing instructions

• Setup master devstack.
• Get lms and cms up using make {lms,cms}-up
• Go to cms shell using make cms-shell
• Run pip install -r requirements/edx/development.txt to install new openedx_events version.
• Exit from cms-shell and see cms logs using make cms-logs.
• Go to studio and delete an xblock or publish a section/subsection.
• This should push the corresponding event to event bus and print below message:

  edx.devstack.cms  | 2023-07-28 13:43:57,201 INFO 515 [edx_event_bus_redis.internal.producer] [user 3] [ip 172.18.0.1] producer.py:82 - Message delivered to Redis event bus: topic=dev-content-authoring-xblock-lifecycle, message_id=cccfef82-2d4c-11ee-9c7a-0242ac12000c, signal=<OpenEdxPublicSignal: org.openedx.content_authoring.xblock.published.v1>, redis_msg_id=b'1690551837201-0'
  

• Play with the EVENT_BUS_PRODUCER_CONFIG by toggling the flag and triggering the event.

Deadline

"None" if there's no rush, or provide a specific date or event (and reason) if there is one.

[navinkarkera]

TODO: update this requirement once openedx/openedx-events#249 is merged

[tecoholic]

@navinkarkera 👍 LGTM. Good to see some code go away :)

• I tested this: Followed the testing instructions and verified that the events are getting published as per the configuration
• I read through the code
• I checked for accessibility issues
• Includes documentation - inline docs present

[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]

Hi @navinkarkera! Flagging the new tests per the recent update: https://discuss.openedx.org/t/minor-change-to-edx-platform-check-statuses/11131

[rgraber]

@navinkarkera how would we feel about leaving events disabled by default until we figure out openedx/openedx-events#265 ?
I can take on that work if you're ok with it.

[navinkarkera]

I can take on that work if you're ok with it.

@rgraber Sure, feel free to create a new PR with the commits or however you see fit.

[rgraber]

I got git into a weird state and ended up just opening another PR here: #33269 . The only things that changed were openedx-events was set to 8.6.0 rather than a branch and all events start disabled in common.py

[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.

[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.