bregctl test: the schema-test runtime cannot run a project with encrypted fields

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
postgresql, rust

调研方向

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 check for this; the limitation disappears with the fix.
主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

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

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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