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

Aperta
#2,647 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
postgresql, rust

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
9h 48m
PR unite (30g)
151

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di registrystack/registry-stack

Tutte le issue di registrystack/registry-stack

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.