refactor: 백엔드 리펙토링 진행 중

This commit is contained in:
DongHyeonka
2026-09-25 17:57:07 +09:00
parent fe80bb3ff3
commit fcddab7e2a
7518 changed files with 3217541 additions and 21259 deletions
+10 -4
View File
@@ -17,10 +17,16 @@ enables the capability; construction is refused otherwise.
## 1. CSFLE
`MongoCsfleProfile` binds a collection to its `MongoCsfleFieldPolicy` list, a key vault
`MongoCredentialReference` and the key vault namespace. `MongoCsfleClientFactory` builds the encrypted
client settings. Data-key selection is the adopter's: `MongoCsfleFieldPolicy.keyAlias()` is the
alias the driver resolves against the key vault.
`MongoCsfleProfile` binds a collection (`database` + `collection`) to its `MongoCsfleFieldPolicy`
list, a key vault `MongoCredentialReference` and the key vault namespace. `MongoCsfleClientFactory`
builds the encrypted client settings from it: the `$jsonSchema` is generated from the field policies
(a dotted path becomes nested `properties`) and keyed by the namespace `database.collection`, and the
key vault client is built from the profile's own credential through `MongoCredentialResolver`.
An automatic-encryption schema names a data key by id, not by alias. The adopter resolves each
`MongoCsfleFieldPolicy.keyAlias()` against the key vault (for example
`ClientEncryption.getKeyByAltName`) and passes the alias → key id map to `settingsFor`; an alias with
no id is refused. Deterministic fields are typed `string` in the schema.
`MongoCsfleMode`: