Build contentstore routing layer and shim [FC-0138]

未关闭
#39,256 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

Start by reading the ADRs in openedx-core PR 880 and issue 890, which describes the backend for the shim. Then trace the existing contentstore API in openedx-platform and determine how routing should reach the legacy store or the shim. Done means new or empty courses support creating, replacing, and deleting files through both paths, without migrating existing files.

由索引模型根据 Issue 内容生成。

描述

Wrap the existing contentstore API in a routing layer that can send requests either to the legacy contentstore, or to the new shim.

Build a contentstore shim that can serve asset requests from openedx_content, using the backend from https://github.com/openedx/openedx-core/issues/890.

Both should be as described in the ADRs (https://github.com/openedx/openedx-core/pull/880).

This should support creating, replacing, and deleting files, but does not yet need to include any migration code for moving existing files over. Test using new/empty courses.

Private ref FAL-4429

主要语言
Python
星标
8.2k
派生
4.4k
平均合并
2 天 10 小时
30 天内合并 PR
40

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

openedx/openedx-platform 的其他 Issue

查看 openedx/openedx-platform 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。