feat: filter by current site organizations

[andrey-canon]

Description

This change filters out course enrollments whose organization is no available for the current site when the site configuration is enabled

I am proposing this change because when an instance contains multiple sites, each of which has access to only specific organizations, there is an issue where the API returns all courses a user is enrolled in, even if the current site does not have access to certain organizations. Although the API offers a query parameter to filter by organization, this parameter only supports one organization at a time, whereas a site may have access to multiple organizations.

Testing instructions

1. Enable site configuration
2. set the course_org_filter value
3. Go to /api/mobile/v4/users/<username>/course_enrollments/ and check that the result doesn't contain any invalid organization

[openedx-webhooks]

Thanks for the pull request, @andrey-canon!

This repository is currently maintained by @openedx/wg-maintenance-edx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[mphilbrick211]

Hi @andrey-canon! Just flagging that there's a failing check here.

[mphilbrick211]

@andrey-canon hi there! Just checking to see if this is still in progress?

[andrey-canon]

@andrey-canon hi there! Just checking to see if this is still in progress?

Hi @mphilbrick211, nop, this is ready for review.

[andrey-canon]

Hi @felipemontoya, @mariajgrimaldi could you please take a look of this ?

[feanil]

@andrey-canon looks like this needs to be rebased off the latest master to get the correct tests running, it looks like it's not running the new static asset shard and is running one too many JS shards.

[andrey-canon]

please take a look of this ?

rebased

[feanil]

@andrey-canon thinking through this a bit more, I think it's worth it to add a test to ensure that the API doesn't break again in the future, can you add a small site-aware test of this endpoint?

[andrey-canon]

@andrey-canon thinking through this a bit more, I think it's worth it to add a test to ensure that the API doesn't break again in the future, can you add a small site-aware test of this endpoint?

@feanil Done

Previous coverage

Current coverage