Third-party technology integration clean-up

[lpalashevski]

Changes in this PR:

• Remove cassandra connectors: cassandra-data-store-connector and cassandra-metadata-extractor-connector Cassandra Dependency (scope/security) #2671
• Remove Data Platform OMAS Remove Data Platform OMAS #5319
• Remove Data Platform Services (governance server, documentation references, assemblies) Remove Data Platform OMAS #5319

[lpalashevski]

Ups, I missed one more reference: cassandra-data-store-connector is used in DataStoreConnectorsArchiveBuilder.

@mandy-chessell Is open-connector-archives module candidate for external repository also?

[mandy-chessell]

Ups, I missed one more reference: cassandra-data-store-connector is used in DataStoreConnectorsArchiveBuilder.

@mandy-chessell Is open-connector-archives module candidate for external repository also?

I expect it needs to be in the repository where the uber-assembly is. At the moment it is only able to create a connector type archive for the data connectors in the main repository

[planetf1]

Ups, I missed one more reference: cassandra-data-store-connector is used in DataStoreConnectorsArchiveBuilder.
@mandy-chessell Is open-connector-archives module candidate for external repository also?

I expect it needs to be in the repository where the uber-assembly is. At the moment it is only able to create a connector type archive for the data connectors in the main repository

Indeed - we need to figure out what we actually want

If it's a complete filesystem tree (think 'egeria-all' !) , we can certainly do that in a distinct repo, similarly to create a connector archive, but who will use them, and how we need to work through, as well as then what each repo 'delivers'

[planetf1]

Super to have this cleaned up. Looks a very thorough proposal

Can we remove the file DataPlatformServicesConfig.java ? Seems to only be for the admin services for data platform & should be removed?
THis also appears in AdminServicesConfigHeader as

        @JsonSubTypes.Type(value = DataPlatformServicesConfig.class, name = "DataPlatformServicesConfig")

which can be removed

[lpalashevski]

Can we remove the file DataPlatformServicesConfig.java ? Seems to only be for the admin services for data platform & should be removed?
THis also appears in AdminServicesConfigHeader as

        @JsonSubTypes.Type(value = DataPlatformServicesConfig.class, name = "DataPlatformServicesConfig")

which can be removed

Initially I had it removed but then put it back beacause there is configuration check in ServerTypeClassifier:

        if (configurationDocument.getDataPlatformServicesConfig() != null)
        {
            throw new OMAGInvalidParameterException(OMAGAdminErrorCode.OLD_CONFIGURATION.getMessageDefinition(serverName,
                                                                                                              configurationDocument.getDataPlatformServicesConfig().toString()),
                                                    this.getClass().getName(),
                                                    methodName);
        }

Let's decide on the call today.

[planetf1]

Suggesting adding a reference to /release-notes/release-notes-2-11.md (see Removed Functionality)

[lpalashevski]

@planetf1 This is now ready to be merged, please do final check.

[planetf1]

I agree these changes are ready to merge