Skip to content

chore: Remove deprecated code owner utilities and related tests - #547

Draft
ktyagiapphelix2u wants to merge 2 commits into
openedx:masterfrom
ktyagiapphelix2u:ktyagi/BOMS-241
Draft

chore: Remove deprecated code owner utilities and related tests#547
ktyagiapphelix2u wants to merge 2 commits into
openedx:masterfrom
ktyagiapphelix2u:ktyagi/BOMS-241

Conversation

@ktyagiapphelix2u

@ktyagiapphelix2u ktyagiapphelix2u commented Aug 10, 2026

Copy link
Copy Markdown

WARNING

The DEPR task list (#469) now clarifies what parts of this PR are unblocked and what is blocked. The blocked parts need to be removed for this to move forward.

Summary

  • Deleted the code owner utility functions and mappings from utils.py, which were no longer in use.
  • Removed the New Relic search script that was dependent on the code owner utilities.
  • Cleared out all associated test files for the code owner functionality, including middleware and utility tests.
  • This cleanup is part of the effort to streamline the monitoring module and remove unused code.

Ticket

https://2u-internal.atlassian.net/browse/BOMS-241

@robrap robrap left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some high-level feedback:

  1. We need to determine whether we will add a deprecation warning before doing this removal.
  2. We want to mark outdated ADRs as obsolete and add a new one to detail why, but ADRs shouldn't be removed.

@ktyagiapphelix2u

Copy link
Copy Markdown
Author
  • We need to determine whether we will add a deprecation warning before doing this removal.

@robrap I’m a bit unclear on this as well. From the original ticket https://2u-internal.atlassian.net/browse/BOMS-241, my understanding was that the deprecation warning should be added after the cleanup/removal work is completed.

Could you clarify what we need to determine before proceeding with the removal, and whether we’re expected to add the deprecation warning before the cleanup instead?

@robrap

robrap commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

@robrap I’m a bit unclear on this as well. From the original ticket https://2u-internal.atlassian.net/browse/BOMS-241, my understanding was that the deprecation warning should be added after the cleanup/removal work is completed.

We can't have a deprecation warning for something that doesn't exist, so it needs to be added before the functionality is deleted. It is the first step, and it also read "possibly after edx-platform clean-up", which I'm not sure why I added, but meant that we could begin removing uses in edx-platform (not definitions from edx-django-utils).

@robrap
robrap marked this pull request as draft August 28, 2026 19:12
@robrap robrap mentioned this pull request Aug 28, 2026
12 tasks
@robrap

robrap commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

[inform] The DEPR task list (#469) now clarifies what parts of this PR are unblocked and what is blocked. The blocked parts need to be removed for this to move forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants