Deprecate Unsupported Libraries

[jmakowski1123]

Abstract

This deprecation work is being undertaken as part of a General Deprecation project funded by tCRIL to expedite a backlog of deprecation debt. The goal of this project is to finish the removal of several unfinished deprecation tickets that we have not been able to complete ourselves due to time constraints.

Project-level metrics:

Impact: Ease of development/time to market.
Measure: DEPR tickets moved to 'Removed' and LOC removed.

Context & Background

We have many deprecation projects in the pipeline and that have been announced to the community, but we don't have the resources to remove all the technology ourselves. We have allotted a general bucket of hours that we can devote to deprecation work to help reduce the pain and complexity of this 'dead' code for future engineers. There are a few general categories of deprecations that we have chosen to focus on:

• Unsupported libraries
• Multiple versions of the same feature
• Incomplete migrations
• MFE replacement work

Scope & Approach

This issue covers the deprecation work that falls into the category of: Unsupported libraries.

• [DEPR]: EdxRestApiClient public-engineering#37

• Goal: Deprecate EdxRestApiClient because it is no longer supported.

Value & Impact

Deprecating unsupported libraries mitigates the potential for future security issues in the library, which would require the deprecation work to be completed regardless, and under more pressing circumstances.

Milestones and/or Epics

see: openedx/public-engineering#37

Named Release

Nutmeg

Timeline

See: openedx/public-engineering#37

Proposed By

tCRIL

Additional Info

No response

[github-actions]

Thanks for your submission, @openedx/open-edx-project-managers will review shortly.

[jmakowski1123]

being tracked in the depr board