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

Offen
#2,647 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
postgresql, rust

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Rust
Sterne
2
Forks
0
Ø Merge
9 Std. 48 Min.
Gemergte PRs (30 T.)
151

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus registrystack/registry-stack

Alle Issues in registrystack/registry-stack

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.