Locations POST has incorrect required fields in Swagger Spec

Incorrect swagger spec requirements for POST Locations

The Locations POST for CDA asks for name and office as required fields

However, when you make a post body of that content you get this error back:

CURL:

curl -X 'POST' \  
'https://SWT-T7:TC-Port/swt-data/locations' \ 
 -H 'accept: */*' \  
-H 'Content-Type: application/json' \  
-d '{  "office-id": "SWT",  "name": "TestLoc_MDP"}'

RESPONSE:

{  
"message": "required fields not present",  
"incidentIdentifier": "user input error",  
"details": {    
  "missing fields": [     
     "horizontal-datum",      
     "timezone-name",     
     "latitude",      
     "location-kind",      
     "longitude"    
    ]
  }
}

Seems it was just forgotten to be added to the swagger spec.

But this is important not only for swagger but also for generators that enforce requirements BEFORE the API call gets made and wasted on a response stating what the wrapper library could have stated.

But this also confused an end user trying to build something into their python code and trying to figure out required fields.

Suggest a single PR to cross check endpoints and cleanup the spec of required fields?

Locate the Swagger/OpenAPI definition for POST /locations and compare its required fields with the backend validation response shown in the issue. Update the contract to include the missing fields, then audit related endpoint requirements; done when the specification matches validation and generated clients can identify all required inputs before making the request.