Background:
The rApp manager enables the rApp designer to create multiple microservices (which expose multiple endpoints from different Kubernetes pods) as part of an rApp.

The rApp designer can decide how these can be exposed. They can choose to expose all endpoints from different microservices, which means that multiple services need to be created in Kong to expose a list of endpoints.

Here, each rApp is considered to be an APF. It can contain any number of AEF profiles, each with its own exposure (endpoints).

Current behaviour:
The rApp designer designs the package with multiple microservices (multiple AEF profiles) and uses it in rApp manager. The SME manager creates a Kong service with the interface description from the first AEFProfile. This leads to service unavailability for the services which are not defined as part of the first AEFProfile.

Expected Behaviour/Solution:
AEFProfile can be iterated, and a Kong service can be created for each interface description inside AEFProfile.

The Kong service name can combine the interface description and resource name as required to make it unique in Kong.