feat: making lms.djangoapps.ccx AppConfig ready.

[alexjmpb]

Description

The CCX app uses a signal receiver (lms.djangoapps.ccx.course_published_handler) to know whenever the outline of a course is updated, the receiver listens to the signal "course_published". Right now, the lms.djangoapps.ccx app does not count with an AppConfig module to import the receivers, and the course_published signal can't be aware of them. This causes an unexpected behavior where the outline of the CCX is not updated. This PR aims to add an apps.py module containing an AppConfig class that imports the signal receivers of the app.

Useful information to include:

• As an useful note, the lms.djangoapps.ccx is not installed in Studio, it should also be added to the INSTALLED_APPS for the signal to be aware of the receiver. Installing lms.djangoapps.ccx also requires to install lms.djangoapps.program_enrollments.

Testing instructions

1. Verify that currently, the CCX outline is not updated whenever the parent course is changed (you can follow the steps 8-11 below to create a CCX).
2. Install a Tutor 17 (https://docs.tutor.edly.io/install.html).
3. Build a custom image using this branch (https://docs.tutor.edly.io/configuration.html#running-a-fork-of-edx-platform).
4. Create a tutor plugin (https://docs.tutor.edly.io/tutorials/plugin.html) that has the following structure.

from tutor import hooks

hooks.Filters.ENV_PATCHES.add_items([
    (
        "openedx-common-settings",
        "FEATURES['CUSTOM_COURSES_EDX'] = True",
    ),
    (
        "openedx-lms-common-settings",
        """
INSTALLED_APPS += ['lms.djangoapps.ccx', 'openedx.core.djangoapps.ccxcon.apps.CCXConnectorConfig', 'user_tasks', 'cms.djangoapps.contentstore.apps.ContentstoreConfig']
COURSE_IMPORT_EXPORT_STORAGE = 'django.core.files.storage.FileSystemStorage'
COURSEGRAPH_DUMP_COURSE_ON_PUBLISH = False
MODULESTORE_FIELD_OVERRIDE_PROVIDERS += ('lms.djangoapps.ccx.overrides.CustomCoursesForEdxOverrideProvider',)
"""
    ),
    (
        "openedx-cms-common-settings",
        """
INSTALLED_APPS += ['lms.djangoapps.ccx', 'lms.djangoapps.program_enrollments']
BULK_EMAIL_DEFAULT_RETRY_DELAY = 30
BULK_EMAIL_MAX_RETRIES = 5
"""
    ),
])

It will suffice to add the settings stated in there to enable all features.

7. Start tutor with the custom image and settings (https://docs.tutor.edly.io/quickstart.html).
8. In studio, create a course and go to advanced settings, once you are there, toggle the "Enable CCX" setting.
9. Go to the course and in the instructor dashboard go to the membership tab and add a CCX coach.
10. Login with your CCX coach, go to the course that you created, go to the CCX coach tab and create a CCX.
11. Now all changes that you make in the parent course outline (sections, subsections) should be reflected in the CCX course. (All the steps to create a CCX can be viewed in the docs https://edx.readthedocs.io/projects/open-edx-building-and-running-a-course/en/latest/set_up_course/studio_add_course_information/custom_courses.html)

[openedx-webhooks]

Thanks for the pull request, @alexjmpb! 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.

[pdpinch]

Is there an issue associated with this PR somewhere? I'd like to know more about the circumstances that lead to its discovery.

[alexjmpb]

Is there an issue associated with this PR somewhere? I'd like to know more about the circumstances that lead to its discovery.

@pdpinch We use the CCX feature in the openedx instances of our organization, and noticed that the outline of the CCXs were not being updated. This issue began after a migration from Juniper to Olive, and we started to debug why this was occurring. After some testings, we found that the task that updates the outline for each CCX (lms.djangoapps.ccx.send_ccx_course_published) was not being called, this was happening due to the issue with the course_published signal commented in the PR description. I then tested this issues in master and found that it's still present.

[Anas12091101]

LGTM

[pdpinch]

@alexjmpb I think this is ready to merge after you fix the quality issue.

[openedx-webhooks]

@alexjmpb 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

[pdpinch]

Thanks @alexjmpb. I hope you don't mind, but I squashed your commits when I merged them. I should have asked you to do this, but I didn't want to add another day or two to this.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[alexjmpb]

Thanks @alexjmpb. I hope you don't mind, but I squashed your commits when I merged them. I should have asked you to do this, but I didn't want to add another day or two to this.

No worries at all. I was thinking of doing the same. Thanks for merging.