Improve the content of connector types (#7103)

[mandy-chessell]

Signed-off-by: Mandy Chessell [email protected]

Description

This PR improves the information captures in a connector provider's connector type:

• The ConnectorProviderBase creates a connector type if it does not exist and fills it out with essential details. It adds the language, implemented interfaces and the connector framework to any connector type it has that has ommitted these details.
• The different types of connector now have a marker interface that identifies which service they run under in Egeria.

Here is an example of a connector type from an integration connector:

Connector Type: Data Files Monitor Integration Connector
    qualifiedName: Egeria:IntegrationConnector:Files:DataFilesMonitor
    description: Connector supports cataloguing of files under a specific directory (folder) in the file system.
    connectorProviderClassName: org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFilesMonitorIntegrationProvider
    recognizedConfigurationProperties:
        templateQualifiedName
        allowCatalogDelete
    connectorInterfaceLanguage: Java
    connectorFrameworkName: Open Connector Framework (OCF)
    connectorInterfaces:
        org.odpi.openmetadata.frameworks.connectors.VirtualConnectorExtension
        org.odpi.openmetadata.frameworks.auditlog.AuditLoggingComponent
        org.odpi.openmetadata.governanceservers.integrationdaemonservices.connectors.IntegrationConnector
        org.odpi.openmetadata.integrationservices.files.connector.FilesIntegratorOMISConnector

Notice the new marker interface FilesIntegratorOMISConnector.

Here is an example from a governance action service:

Connector Type: Move or Copy File Governance Action Service
    qualifiedName: Egeria:GeneralGovernanceActionService:Provisioning:MoveCopyFile
    description: Provisioning Governance Action Service that moves or copies files on request.
    connectorProviderClassName: org.odpi.openmetadata.adapters.connectors.governanceactions.provisioning.MoveCopyFileGovernanceActionProvider
    recognizedConfigurationProperties:
        targetFileNamePattern
        noLineage
        topLevelProcessQualifiedName
        topLevelProcessTemplateQualifiedName
        destinationFileTemplateQualifiedName
        destinationFolder
        topLevelProcessLineageOnly
        lineageFromSourceFolderOnly
        lineageToDestinationFolderOnly
    connectorInterfaceLanguage: Java
    connectorFrameworkName: Open Connector Framework (OCF)
    connectorInterfaces:
        org.odpi.openmetadata.frameworks.connectors.VirtualConnectorExtension
        org.odpi.openmetadata.frameworks.auditlog.AuditLoggingComponent
        org.odpi.openmetadata.frameworks.governanceaction.GovernanceActionService

Notice marker interface GovernanceActionService.

Finally, I uncovered a bug in the templating - the new entity was unsing the caller type information, not that from the template entity - this meant that it was being created with a more generic type and some of the properties from the template could be invalid.

Related Issue(s)

#7103

Testing

Using the new Governance Server Lab.

Release Notes & Documentation

No more than needed for the original feature

Additional notes