Initiate DEPR of CookieNameChange middleware

[robrap]

The code in question is:

• https://github.com/openedx/edx-platform/blob/eb03cfbe535c6c194eba21586ea4947fb8123c9d/openedx/core/djangoapps/cookie_metadata/middleware.py#L65

We probably have observability to ensure it is no longer being used, but it shouldn't be.

This code probably should have been plugged-in as our own middleware in the first place. It is not a utility that is specific to edx-platform.

Here is the OEP for DEPR: https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0021-proc-deprecation.html

[robrap]

I checked and COOKIE_NAME_CHANGE_ACTIVATE, which is defaulted to False, doesn't seem to be set for us 2U. So we are not using the middleware. See:

• https://github.com/openedx/edx-platform/blob/489385e186d57a8d53b02c737ee33376f013a77c/openedx/core/djangoapps/cookie_metadata/middleware.py#L60-L69.

[robrap]

See https://github.com/openedx/open-edx-proposals/blob/60d6209d51c7b84c11ccd8535c79da20345c52df/oeps/processes/oep-0021-proc-deprecation.rst for more clarity about how to start the process. You want to create a Draft issue in github, and announcing will come next. Thanks!

[robrap]

@ktyagiapphelix2u: Are next steps clear? Thank you.

[robrap]

@ktyagiapphelix2u: It would also be good to update status of this ticket on this ticket.

For example, you could have noted here that you announced the DEPR here: https://discuss.openedx.org/t/deprecation-removal-cookienamechange-middleware-edx-platform-1003/16144. (This is probably a better place than Slack, although in Slack we could discuss further, and you can ping me as well as needed.)

[robrap]

Some additional notes copied from this Slack thread:

1. No need for a deprecation warning, since the early deployers (like 2U) are not using this, and operators on named releases of the platform would never see the warning, because the plan would be to remove this in the next release.
2. Creating the Draft DEPR issue in github is the next step.
3. Preparing the removal PR is also possible, although we wouldn't merge it until the DEPR process moved forward.

[ktyagiapphelix2u]

I wanted to provide an update on the status of this deprecation:

1. I have announced the deprecation of CookieNameChange middleware on the Open edX discussion forum: https://discuss.openedx.org/t/deprecation-removal-cookienamechange-middleware-edx-platform-1003/16144

2. I have created a PR to implement the removal: [DO NOT MERGE] fix! : [DEPR] Remove deprecated CookieNameChange middleware openedx/edx-platform#36815

3. As discussed, we determined that no deprecation warning is necessary since early deployers like 2U are not using this functionality, and operators on named releases wouldn't see the warning as it will be removed in the next release.

4. I've created a draft DEPR issue (#36834) at [DEPR]: Remove CookieNameChange middleware openedx/edx-platform#36834 to formally document the deprecation and removal process following OEP-21 guidelines.

Please let me know if there are any additional steps needed to move this deprecation forward.