Make CatalogTarget relationship multi-link

[mandy-chessell]

Description

For the Unity Catalog integration connectors, we need to establish multiple CatalogTarget relationships between the Unity Catalog Server entity and the OSSUnityCatalogInsideCatalogSync integration connector entity (one for each catalog).

This means the CatalogTarget type definition needs to be set to multi-link and the REST API for managing catalog target relationships has to change to:

• allow the relationship GUID to be passed on the getCatalogTarget, updateCatalogTarget and deleteCatalogTarget methods
• return the relationshipGUID on the createCatalogTarget

These API changes affect:

• Automated Curation OMVS
• Governance Engine OMAS
• Open Integration Framework Services

@fyi @dwolfson

Related Issue(s)

• The release of 5.0 libraries to maven central identified a build.gradle file (GUIDGenerator) that did not have a description. This has been added.

• Templates for the different types of files were using a placeholder variable for the deployedImplementationType attribute which has the follow problems:

  • The calling user has to set it - annoying - and they may get it wrong.
  • The method in Automated Curation OMVS that allows templates to be queried by technology type (ie deployedImplementationType) was not finding the file templates.

This is now fixed in the CoreContentpack.

The GitHub workflows for merge and release are no longer publishing the egeria-configure container as we no longer need it.

Testing

Lots of manual testing through the OSS Unity Catalog connectors.

Release Notes & Documentation

The change to the CatalogTarget relationship is now inthe release notes.

Additional notes

None