feat: [AXM-2307] add management command to backfill ContentDate model…

[kyrylo-kh]

… with existing assignments

NOTE: Depends on: openedx/edx-when#347

Description

This PR adds a new Django management command seed_content_dates that extracts assignment due dates from the modulestore and populates the ContentDate table in the edx-when service.

Key Features

• Command: python manage.py lms seed_content_dates
• Backfills assignment due dates into ContentDate from course assignments in the modulestore.

Options

• --course-id: Seed a specific course.
• --org: Seed all courses for a specific organization.
• --dry-run: Simulate processing without writing to the database.
• --force-update: Overwrite existing ContentDate records instead of skipping.
• --batch-size: Process assignments in batches (default: 100).

Example Usage

# Dry run for all courses
python manage.py lms seed_content_dates --dry-run

# Process a specific course
python manage.py lms seed_content_dates --course-id "course-v1:MITx+6.00x+2023_Fall"

# Process all courses for an organization
python manage.py lms seed_content_dates --org "MITx"

# Force update existing records
python manage.py lms seed_content_dates --force-update

[openedx-webhooks]

Thanks for the pull request, @kyrylo-kh!

This repository is currently maintained by @openedx/wg-maintenance-openedx-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.

Details

---

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.

[e0d]

A general comment: there are no tests for this new command.

[e0d]

Why aren't we using the batch capability of the imported function rather than running this in a loop with single item lists?

[kyrylo-kh]

Re-implemented in batch way

[e0d]

Why this broad catch and continue? I think this is problematic because Django, I believe, will mark the atomic transaction that you created above as invalid and all of the updates will ultimately fail. If the idea is to make this save as much as possible, you will have to change the transaction boundaries.

[kyrylo-kh]

Removed the outer atomic() around the course; each batch is its own atomic(); failures are handled outside that block.

[e0d]

We shouldn't be reaching in to when's models directly. If there isn't an API that currently supports this, we should create it.

[kyrylo-kh]

Switched to get_existing_due_locations() on edx_when.api (added there).

[e0d]

This pattern is unacceptable in my opinion. We need a more robust approach that doesn't pick any old staff user for the convenience of the management command.

[kyrylo-kh]

Replaced with required --username and validation (is_staff, is_active).

[e0d]

I'm not sure of the current performance of this, but passing it as an argument seems like the right thing to do.

[kyrylo-kh]

Re-implemented and now it's called once and the store is passed into _process_course

[kyrylo-kh]

Tests are failing because they depends on openedx/edx-when#346. This should be merged after merging edx-when PR