Skip to content

Commit 20a50da

Browse files
DOCSP-22176 - Adding delete key section (#1370)
* adding delete key section * removed getMongo()
1 parent e3922df commit 20a50da

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

source/core/csfle/fundamentals/manage-keys.txt

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
.. DOCSP-22176: Move the data key delete ref to the location
22
of this content once the content is added.
33

4-
.. _field-level-encryption-data-key-delete:
54
.. _field-level-encryption-data-key-manage:
65
.. _csfle-fundamentals-manage-keys:
76

@@ -267,6 +266,26 @@ As a result, the ``salary`` fields in the two example documents are
267266
uniquely encrypted using {+dek-long+}s specific to the individual
268267
document. The keys are assigned dynamically at runtime.
269268

269+
.. _field-level-encryption-data-key-delete:
270+
271+
Delete a {+dek-long+}
272+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
273+
274+
You can delete a {+dek-abbr+} from your {+key-vault-long+} using standard CRUD
275+
:ref:`delete operations <write-op-delete>`.
276+
277+
.. tip:: MongoDB Shell Specific Feature
278+
279+
The MongoDB shell allows you to delete a {+dek-abbr+} by ``UUID`` using
280+
the ``keyVault.deleteKey()`` method as follows:
281+
282+
.. code-block:: none
283+
284+
keyVault = db.getKeyVault()
285+
keyVault.deleteKey(UUID("<UUID String>"))
286+
287+
To learn more about {+key-vault-long+}s see :ref:`csfle-reference-key-vault`.
288+
270289
Learn More
271290
----------
272291

0 commit comments

Comments
 (0)