WellboreTrajectory can be created with a non-existing WellboreID
Current postman collection for pre-ship testing creates a WellboreTrajectory with a typo in the WellboreID. The Trajectory is created even though the WellboreID does not exist. So there is no referential integrity check being performed when creating a Trajectory with POST https://{{WELLBORE_DDMS_HOST}}/ddms/v3/wellboretrajectories. The body has this:
"id": "{{data-partition-id}}:work-product-component--WellboreTrajectory:{{WellboreDMSRunId}}", "kind": "{{authority}}:{{schemaSource}}:work-product-component--WellboreTrajectory:1.1.0", "data": { "Name": "Wellbore_Trajectory_{{WellboreDMSRunId}}", "WellboreID": "{{data-partition-id}}:master-data--Wellbore::{{WellboreDMSRunId}}:",
Which has typo of double colon after Wellbore.
The WPC for WellboreTrajectory is successfully created however the WellboreID is invalid and the record does not exist.Using GET https://{{WELLBORE_DDMS_HOST}}/ddms/v3/wellbores/osdu:master-data--Wellbore::AutoTest_999130548486:
{ "origin": "osdu-data-ecosystem-storage", "errors": [ { "code": 404, "reason": "Record not found", "message": "The record 'osdu:master-data--Wellbore::AutoTest_999130548486' was not found" } ] }
Link to postman collection is here:
THis was found using M17 pre-ship environment.