Public Access
jaap-jan
eaf68c86b0
Schema for identity, vaults, grants, hosts and the sync change log, verified against a real PostgreSQL 18 container rather than an in-memory provider: partial unique indexes, CHECK constraints, citext and identity-always columns are all provider behaviour that an in-memory fake would not exercise. Invariants pushed into the database, so they hold even when application code has a bug: - ck_host_relay_target is a security boundary, not tidiness. A host may carry a plaintext hostname and port ONLY when relay is deliberately enabled. Both directions are tested; the important one is that relay-disabled hosts cannot carry an address, since otherwise a bug would silently give the server infrastructure visibility it was never granted. - ck_vault_owner: exactly one of owner_user_id or team_id, or permission resolution would have no defined answer. - ck_vault_key_grant_recipient: member grants name a user; recovery and escrow grants are wrapped to a key and must not. - ck_user_key_wrap_kdf: a password-derived wrap without its parameters is permanently unopenable, so a partial write is rejected outright. Present from the first migration on purpose: - GrantKind (Member/Recovery/Escrow). Recovery cannot be bolted on later — every vault created before it existed would be unrecoverable by design. - team and team_membership, though team features are M3. Adding them later would mean introducing a foreign key on a live vault table. - Host.ContentKeyId, reserved for per-item content keys wrapped to individual users. - user_key as its own table, so key rotation does not require altering the user row. Two things verified rather than assumed: - Npgsql's UseXminAsConcurrencyToken helper no longer exists in EF 10, so xmin is mapped directly in XminConcurrency. The generated migration *looks* like it creates an xmin column; it does not. Confirmed by inspecting pg_attribute (attnum -2, a system column) and by grepping the emitted DDL. A test pins both, because had it created a real column PostgreSQL would have rejected the name. - EF Core is now pinned centrally. The Npgsql provider asks for 10.0.4 while EntityFrameworkCore.Design pulls 10.0.10, and because Design is PrivateAssets=all that higher version does not flow to referencing projects — producing a CS1705 in any test project referencing Infrastructure. Also commits artifacts/schema/v0.1.sql, the idempotent script, as the baseline for future upgrade tests. Verified: 0 warnings, 122 tests pass (27 new against Postgres), format clean.
29 lines
1.1 KiB
XML
29 lines
1.1 KiB
XML
<Solution>
|
|
|
|
<Folder Name="/solution items/">
|
|
<File Path="Directory.Build.props" />
|
|
<File Path="Directory.Packages.props" />
|
|
<File Path="BannedSymbols.txt" />
|
|
<File Path=".editorconfig" />
|
|
<File Path="NuGet.config" />
|
|
<File Path="global.json" />
|
|
<File Path=".gitattributes" />
|
|
</Folder>
|
|
|
|
<Folder Name="/src/">
|
|
<Project Path="src/DodoSSH.Contracts/DodoSSH.Contracts.csproj" />
|
|
<Project Path="src/DodoSSH.Crypto/DodoSSH.Crypto.csproj" />
|
|
<Project Path="src/DodoSSH.Domain/DodoSSH.Domain.csproj" />
|
|
<Project Path="src/DodoSSH.Infrastructure/DodoSSH.Infrastructure.csproj" />
|
|
<Project Path="src/DodoSSH.Api/DodoSSH.Api.csproj" />
|
|
</Folder>
|
|
|
|
<Folder Name="/tests/">
|
|
<Project Path="tests/DodoSSH.Contracts.Tests/DodoSSH.Contracts.Tests.csproj" />
|
|
<Project Path="tests/DodoSSH.Crypto.Tests/DodoSSH.Crypto.Tests.csproj" />
|
|
<Project Path="tests/DodoSSH.Domain.Tests/DodoSSH.Domain.Tests.csproj" />
|
|
<Project Path="tests/DodoSSH.Infrastructure.Tests/DodoSSH.Infrastructure.Tests.csproj" />
|
|
</Folder>
|
|
|
|
</Solution>
|