chore!: removing lx-pathway-plugin from private requirements - #7030
Conversation
|
@awais786 Your current plan would be:
I imagine steps 3-6 would never be done, and we would never remove the tables, or SRE would have to do it.
Let me know if you disagree. |
adzuci
left a comment
There was a problem hiding this comment.
@awais786 Could we follow the normal process here to avoid setting a poor precedent even though we are confident this code is not in use? https://openedx.atlassian.net/wiki/spaces/COMM/pages/1051361376/Removing+a+Djangoapp+from+an+existing+project
3d16ea6 to
43c3b06
Compare
|
@connorhaugh its ready to go. |
UsamaSadiq
left a comment
There was a problem hiding this comment.
Verified the commit hash to be the latest master hash from the repository.
|
@adzuci your requested changes implemented. |
connorhaugh
left a comment
There was a problem hiding this comment.
Looks good thank you for following the safest process here!
This Package is no more in use. Need to remove this or update due to
django42compatiblity.Since mysql8 backup still going on. So instead of deleting table i am removing this package from installation. After backup completion will remove the tables completely.conversation about removing/deleting tables open-craft/lx-pathway-plugin#1 (comment)
They merged PR with deletion table migration.