feat: [FC-0044] group configurations API DRF

[ruzniaievdm]

Settings

TUTOR_GROVE_WAFFLE_FLAGS:
  - name: contentstore.new_studio_mfe.use_new_group_configurations_page
    everyone: true

Description

This PR addresses a need in the development of the Course Group Configurations Page feature within the frontend-app-course-authoring repository. The core objective is the implement of a DRF endpoint designed to render and deliver group configurations data for course.

Learn about group configurations:

• How to activate content experiments configure: https://edx.readthedocs.io/projects/open-edx-building-and-running-a-course/en/latest/course_features/content_experiments/content_experiments_configure.html#id11
• How to add content group: https://edx.readthedocs.io/projects/open-edx-building-and-running-a-course/en/latest/course_features/cohorts/cohorted_courseware.html#content-groups
• Creating Course Content for Specific Enrollment Tracks https://edx.readthedocs.io/projects/open-edx-building-and-running-a-course/en/latest/course_features/diff_content/enroll_track_courseware.html

Group Configurations Pages:

1. Legacy cms - http://localhost:18010/group_configurations/{location}.
2. MFE - http://localhost:2001/course/{location}/group_configurations.

Testing API instructions:

1. Run master devstack.
2. Start platform make dev.up.lms+cms and make checkout on this branch.
3. Go to http://localhost:18010/api-docs.
4. Find the required API endpoint /api/contentstore/v1/group_configurations/{location}.

Testing MFE instructions:

1. Run master devstack.
2. Start platform make dev.up.lms+cms+frontend-app-course-authoring and make checkout on this branch.
3. Enable the MFE Group Configurations Page feature by adding a waffle flag contentstore.new_studio_mfe.use_new_group_configurations_page on the http://localhost:18010/admin/waffle/flag/
4. Go to http://localhost:2001/course/{location}/group_configurations.

Group configurations issue

openedx/platform-roadmap#318

[openedx-webhooks]

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

[openedx-webhooks]

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

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

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

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