Some requests in Well Delivery postman collection fail, because of hard code values.

Use the provided collection with five use cases (UC1-UC5) and define the following variable to match the environment

SchemasURL = https://osdu-ship.msft-osdu-test.org/api/schema-service/v1/schema welldeliveryURL = https://osdu-ship.msft-osdu-test.org/api/well-delivery schemaHost = https://osdu-ship.msft-osdu-test.org apisHost = https://osdu-ship.msft-osdu-test.org dataPartitionID data-partition-id value e.g. opendes for azure aclViewers data.default.viewers@{{data-partition-id}}{{domain}} e.g. for azure data.default.viewers@opendes.contoso.com aclOwners data.default.owners@{{data-partition-id}}{{domain}} data.default.owners@opendes.contoso.com
legalTags pick any legal tag value in your environment opendes-public-usa-dataset-7643990 bearerToken assign value of access_token from the refresh token request

Once the expected environment was defined the collection ran fine with the following results Requests that failed - status return was not successful.

UC1 well_activity_programs_specific_version_get_by_well GET {{welldeliveryURL}}/wellActivityPrograms/v1/by_well/welldemo2/1638220411920 version value is hardcoded. Response: 404 Not Found

UC2 activity_plans_by_well GET {{welldeliveryURL}}/activityPlans/v1/by_well/welldemo1 mismatch between the ids (UC1 create well and UC2 get activity plans by well) Response: 404 Not Found

UC3 query_BHArun_by_well POST {{welldeliveryURL}}/query/v1/by_well/bhaRun:batch Response: 404 Not Found { "message": "Could not find BHA run with wellbore id: wellbodemo2" }

UC3 query_wellboreTrajectory_by_well POST {{welldeliveryURL}}/query/v1/by_well/wellboreTrajectory:batch Response: 404 Not Found { "message": "Could not find wellbore with well id: welldemo1" }

UC4 holeSection_by_wellbore GET {{welldeliveryURL}}/holeSections/v1/by_wellbore/wellboredemo02 Response: 404 Not Found { "message": "Not found wellbore segments with wellbore id :wellboredemo02" }

			GET	{{welldeliveryURL}}/bhaRuns/v1/by_holeSection/holesectiondemo3
			Response: 404 Not Found
			{
				"message": "Not found planned BHA runs with wellbore segment id :holesectiondemo3"
			}

UC5 well_activity_programs_version_reference_tree GET {{welldeliveryURL}}/wellActivityPrograms/v1/reference_tree/by_well/welldemo2/1638305706168 { "message": "Could not find specific well activity program with well id: welldemo2 well activity program version : 1638305706168" }

		version value is hardcoded. 
		Response: 404 Not Found