Minimize configured topics for Access Services (OMASs)

[mandy-chessell]

Description

Except when the "no-topics" option is specified, the access services configuration helper methods add a connection for both the InTopic and the OutTopic to each access service configuration irrespective of whether the particular OMAS supports these topics.

This has no impact at runtime because the OMASs simply do not start topics they do not use. However, from a set up point of view, it is misleading - and can result in an organization thinking they need to set up (and may be pay for) topics that are not use.

This PR adds knowledge of whether an OMAS supports the inTopic and/or OutTopic to AccessServiceDescription. This information is used by the configuration helper methods when setting up the access service configuration.

Related Issue(s)

None

Testing

Using the "Understanding server configuration" open metadata lab I checked that the configuration documents no longer contain unnecessary topic connections.

This is the list of topics for cocoMDS1 after the change:

List of Topics used by cocoMDS1
  egeria.omag.server.cocoMDS1.omas.assetcatalog.outTopic
  egeria.omag.server.cocoMDS1.omas.assetconsumer.outTopic
  egeria.omag.server.cocoMDS1.omas.assetmanager.outTopic
  egeria.omag.server.cocoMDS1.omas.assetowner.outTopic
  egeria.omag.server.cocoMDS1.omas.communityprofile.outTopic
  egeria.omag.server.cocoMDS1.omas.dataengine.inTopic
  egeria.omag.server.cocoMDS1.omas.datamanager.outTopic
  egeria.omag.server.cocoMDS1.omas.digitalarchitecture.outTopic
  egeria.omag.server.cocoMDS1.omas.governanceengine.outTopic
  egeria.omag.server.cocoMDS1.omas.assetlineage.outTopic

Notice Data Engine OMAS supports an InTopic only. All of the others support just an OutTopic. Prior to this change, each OMAS had both an InTopic and an OutTopic configured.

Release Notes & Documentation

The description from this PR is summarized in the R4.2 release notes.