[DRIVERS-2376] Clarify expected bulk write operations for rewrapManyDataKey Created: 28/Jun/22 Updated: 28/Oct/23 Resolved: 29/Jun/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Client Side Encryption |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Ezra Chung | Assignee: | Ezra Chung |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Not Needed | ||||||||
| Description |
SummaryThe CSE spec does not fully describe what bulk write operations are expected given a call to ClientEncryption.rewrapManyDataKey(). The CSE spec should capture the expectations currently expressed only as assertions in unified spec tests. MotivationWho is the affected end user?Drivers implementing ClientEncryption.rewrapManyDataKey(). How does this affect the end user?Clarification of expected bulk write operations in CSE spec may reduce confusion or opportunity for surprise during implementation. How likely is it that this problem or use case will occur?N/A If the problem does occur, what are the consequences and how severe are they?Minor. Is this issue urgent?No. Is this ticket required by a downstream team?No. Is this ticket only for tests?No. This clarifies expectations of implementation of ClientEncryption.rewrapManyDataKey(). |
| Comments |
| Comment by Githook User [ 29/Jun/22 ] |
|
Author: {'name': 'Ezra Chung', 'email': '88335979+eramongodb@users.noreply.github.com', 'username': 'eramongodb'}Message: |