In Azure Pre-ship R3 M9 environment the postman search collection with requests that have nested keyword in them are failing with status code of 400 Bad Request.
curl --location --request POST 'https://osdu-ship.msft-osdu-test.org/api/search/v2/query'
--header 'Content-Type: application/json'
--header 'data-partition-id: opendes'
--header 'Authorization: Bearer eyJ0eXAiOiJKV1Qi...-TbfMg-eg'
--data-raw '{
"kind": "osdu:wks:master-data--Well:1.0.0",
"query": "data.DefaultVerticalMeasurementID: * OR nested(data.VerticalMeasurements, (VerticalMeasurementID:(*)))"
}'
Response: { "code": 400, "reason": "Bad Request", "message": "Invalid parameters were given on search request" }
The same requests when run on AWS and GCP run fine without any errors. Also one time even on Azure they were giving correct results. I do not know what has changed to see this behavior at present. One can use the collection from the Platform Validation project (https://community.opengroup.org/osdu/platform/testing/-/blob/master/Postman%20Collection/37_CICD_R3_SearchAPI/Search%20API%20R3%20CI-CD%20v1.0.postman_collection.json)
In the above collection look at the request with the name starting with: C04, C05, C06, C07 The curl command for request C04 is provided above. @ankurrawat @krganesan @manishk @PrashanthK @ChrisZhang @debasisc @kumar_vaibav @krveduru