bregctl test: the schema-test runtime cannot run a project with encrypted fields
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
调研方向
Read crates/registry-breg/src/fixtures.rs and compare SchemaTestRuntime::new with startup setup in crates/registry-breg/src/startup.rs; trace how mutations report FieldEncryptionUnavailable in crates/registry-breg/src/mutation.rs. Start by locating the schema-test runtime's encryption setup and related fixture journey tests. Done means a journey can create, read, and list a Record with an encrypted field, while the ephemeral key is neither written to disk nor printed.
由索引模型根据 Issue 内容生成。
描述
Problem
bregctl test (and rstack dev start, which runs the project's journeys through the same schema-test runtime) fails for any project whose Record types use field encryption. A journey that writes an encrypted field gets 503 with runtime.field_encryption.unavailable.
Cause
SchemaTestRuntime::new in crates/registry-breg/src/fixtures.rs builds the record, revision, snapshot and mutation services without with_field_encryption, unlike startup (crates/registry-breg/src/startup.rs). A mutation on an encrypted type then fails with MutationError::FieldEncryptionUnavailable (crates/registry-breg/src/mutation.rs), which the API maps to the fixed RuntimeFieldEncryptionUnavailable problem.
Consequence
An author cannot test a project with encrypted fields offline, and rstack dev cannot run its journeys either. The only workaround is to remove the encryption from the project under test, which tests a different project.
Suggested fix
Give the schema-test runtime field encryption with an ephemeral, in-memory key generated per test run. Its database is disposable, so the key needs no custody beyond the process. Keep the key out of reports and logs.
Done when
- A fixture journey that creates, reads and lists a Record with an encrypted field passes under
bregctl test. - The test runtime never writes the key to disk or prints it.
- No static warning is added to
rstack dev checkfor this; the limitation disappears with the fix.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 151
环境准备
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
registrystack/registry-stack 的其他 Issue
-
area:breg enhancement
难度 2/5 1-3 小时 新手友好度 65/100
registrystack/registry-stack#2765 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
registrystack/registry-stack#2761 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
registrystack/registry-stack#2743 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
registrystack/registry-stack#2706 ·
维护者通常 1 天内回复
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directory未关闭
难度 2/5 1-3 小时 新手友好度 83/100
registrystack/registry-stack#2704 ·
维护者通常 1 天内回复
查看 registrystack/registry-stack 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 82/100
stackabletech/airflow-operator#898 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)可能已有人在做 @zyl71 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100