Pipeline API renamed configuration details

[Nils-Schiwek]

We are using the pipeline API in one of our projects and it is currently breaking, as it seems the pipeline API has changed without further notice.

We are expecting the pipeline API to use the following structure, as documented in the MSSharePointConfiguration schema:

        "id": "fake-id",
        "type": "MSSharePoint",
        "configuration": {
            "destination": "destination-name",
            "sharePoint": {
                "site": {
                    "id": "internal.sharepoint.com,fake-id,fake-id",
                    "name": "secret-id",
                    "includePaths": []
                }
            }
        }

But recent responses are formatted as:

        "id": "fake-id",
        "type": "MSSharePoint",
        "configuration": {
            "destination": "destination-name",
            "share_point": {
                "site": {
                    "id": "internal.sharepoint.com,fake-id,fake-id",
                    "name": "secret-id",
                    "include_paths": []
                }
            }
        }

So the API is returning share_point instead of sharePoint (as in the past). I expect this to be an error on the API level, as it is not documented anywhere.