-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Description
@BobWall23 reported in slack:
The TSP integration tests broke with the switch to the official Azure client (#991) - commit 95df28c88b695a4a4067fa98262318e798fbbc46.
Haven't figured out exactly where - lots of changes.
The integration test fails with this:
● INTEGRATION dev environment tests › test Azure key version protobuf › fails with expected error when edek looks like protobuf, but isnt
expect(received).toContain(expected) // indexOf
Expected substring: "Failed to unwrap key via Azure"
Received string: "Azure request failed with an unexpected error: { status: BadRequest, error_code: Some(\"400\"), raw_response: Some(RawResponse { status: BadRequest, headers: {\"x-ms-request-id\": \"7b08dffb-b195-4ac5-9621-e562f237654b\", \"x-content-type-options\": \"REDACTED\", \"cache-control\": \"no-cache\", \"x-ms-client-request-id\": \"49272d66-0d60-43f8-9e46-7a6a5e5d8432\", \"content-length\": \"77\", \"pragma\": \"no-cache\", \"expires\": \"-1\", \"x-ms-keyvault-service-version\": \"REDACTED\", \"strict-transport-security\": \"REDACTED\", \"content-type\": \"application/json; charset=utf-8\", \"x-ms-keyvault-region\": \"REDACTED\", \"x-ms-keyvault-network-info\": \"REDACTED\", \"date\": \"Wed, 03 Dec 2025 21:04:50 GMT\"}, body: ResponseBody }) }"
The message that is returned is not what is expected - not clear if the response from Azure (or the request sent to Azure) were different.
Determined that this was changed by the change to the official azure client in the TSP. Decided to just fix the integration test in node.
Metadata
Metadata
Assignees
Labels
No labels