mirror of
https://github.com/spring-projects/spring-data-mongodb.git
synced 2026-05-03 03:34:23 +01:00
Fix markup in encryption documentation.
Closes: #5030 Signed-off-by: atandon2024 <ajay.tandon@mongodb.com>
This commit is contained in:
committed by
Christoph Strobl
parent
829c15a9bf
commit
5a733c464c
@@ -146,7 +146,7 @@ It's useful when you need to explicitly manage data keys, encryption algorithms,
|
||||
** ✅ Explicit configuration avoids the risk of surprises (e.g. missing configuration because of improper annotations or class-path scanning)
|
||||
** ⚠️ An Explicit Field Configuration can diverge from the domain model and you must keep it in sync with the domain model
|
||||
|
||||
**Derived setup*
|
||||
**Derived setup**
|
||||
|
||||
Derived setup relies on annotations in your domain model and automatically generates the required encrypted field configuration from it.
|
||||
This is simpler and recommended for typical Spring applications where your data model is already annotated.
|
||||
|
||||
Reference in New Issue
Block a user