[DOCS-13041] Investigate changes in SERVER-43005: getKeyVault.createKey() should return the created data key Created: 20/Sep/19  Updated: 13/Nov/23  Resolved: 31/Oct/19

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ravind Kumar (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-43005 getKeyVault.createKey() should return... Closed
Participants:
Days since reply: 4 years, 16 weeks, 2 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

Changes noted in the description.

Description of Linked Ticket

In 4.2.0, the getKeyVault.createKey() method returns a WriteResult instead of the created key. This requires users to do one of two things:

  • Search by key alternate name for the created key, or
  • Search all keys in reverse creation order for the most recently created key

As noted in the spec document, data key creation methods should return at least the _id of the created document.

The 4.2 shell should either return the _id of the created data key per-spec.

 

Relevant code here

 

cc shreyas.kalyan

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 21/Oct/19 ]

Author:

{'email': 'ravind.kumar@mongodb.com', 'name': 'Ravind Kumar'}

Message: DOCS-13041: KeyVault.createKey() returns UUID, other fixups
Branch: master
https://github.com/mongodb/docs/commit/a04f5ab180cb9bea231f636ed9a24f009966f8da

Generated at Thu Feb 08 08:06:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.