[MONGOCRYPT-348] Separate KMS provider specific fields in kms_response_parser_t Created: 16/Oct/21  Updated: 25/Oct/22

Status: Backlog
Project: Libmongocrypt
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Background & Motivation

kms_response_parser_t represents a KMS provider generic response parser. It applies to providers that use HTTP (AWS, Azure, and GCP) as well as KMIP. The KMIP parser is separated into an internal kms_kmip_response_parser_t. However, the HTTP parsing logic is still within the functions of kms_response_parser_t. Separating the HTTP parsing logic would help with code readability.

Scope
Move the HTTP parsing code into a separate kms_http_response_parser_t to have a better separation of parsing logic. And have functions like kms_response_parser_feed delegate to kms_http_response_parser_feed or kms_kmip_response_parser_feed depending on the parser type.


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