[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: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 4 years, 16 weeks, 2 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary Changes noted in the description. Description of Linked TicketIn 4.2.0, the getKeyVault.createKey() method returns a WriteResult instead of the created key. This requires users to do one of two things:
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.
Scope of changesImpact to Other DocsMVP (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: |