Implemented File DMS APIs

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)
#29 (closed)

Related OS-Core-Common MR - osdu/platform/system/lib/core/os-core-common!99 (diffs)

Does this introduce a change in the core logic?

• [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

N/A

What is the new/expected behavior?

Added Get Storage Instructions API for File DMS. Sample response is as follows for Azure implementation

{
    "providerKey": "AZURE",
    "storageLocation": {
        "signedUrl": "<Signed URL>",
        "fileSource": "<File Path>",
        "createdBy": "osdu-user"
    }
}

Added Get Retrieval Instructions API implementation for File DMS. Sample Response is as follows for Azure implementation

{
    "providerKey": "AZURE",
    "datasets": [
        {
            "datasetRegistryId": "id1",
            "retrievalProperties": {
                "signedUrl": "<signed url for download>",
                "createdBy": "osdu-user"
            }
        },
        {
            "datasetRegistryId": "id2",
            "retrievalProperties": {
                "signedUrl": "<signed url for download>",
                "createdBy": "osdu-user"
            }
        }
    ]
}

Added Copy DMS API. Sample response will be as follows

[
    {
        "success": true,
        "datasetBlobStoragePath": "<Blob Store endpoint>/osdu-user/1626087994933-2021-07-12-11-06-34-933/a399493fbd2d4678a35ac816e9a92153"
    }
]

Have you added/updated Unit Tests and Integration Tests?

• Added P0 Integration tests for the newly added APIs.
• Added Unit tests.

Any other useful information