Standardization of endpoints

Summary

Based on the recent M19 pre-shipping testing, we identified a few discrepancies in the Reservoir DDMS endpoints for both ETP and REST servers. We need to follow the standard convention of OSDU.

Actual behavior

These are the endpoints observed today.

ETP Server:

• [AWS] wss://osdu.r3m18.preshiptesting.osdu.aws/api/oreservoir-ddms-etp/v2/
• [Azure] wss://osdu-ship.msft-osdu-test.org/oetp/reservoir-ddms/
• [Google] wss://preship.gcp.gnrg-osdu.projects.epam.com/api/oetp-server/v2/
• [IBM] ?

REST Server:

• [AWS] https://osdu.r3m18.preshiptesting.osdu.aws/api/reservoir-ddms/v2
• [Azure] https://osdu-ship.msft-osdu-test.org/api/oetp-client/v2
• [Google] https://preship.gcp.gnrg-osdu.projects.epam.com/api/reservoir-ddms/v2
• [IBM] ?

Intended behavior

We should follow the standard endpoint convention in OSDU.

ETP Server:

• {baserurl}/api/reservoir-ddms-etp/v2/

REST server:

• {baserurl}/api/reservoir-ddms/v2/{methods}

Pending Implementation

• AWS
• Azure
• GC
• IBM