[Bug] Data Product Parser - Ports reference generation

[RiccardoAmbrosini]

Parser Issue - Ports api link conflicts

While registering a data product to the ODM registry, the server generates a fully qualified name for the api object within a port's promise based on its name and version. The issue is that if on the same registry there are two apis with the same name and version, the linked reference of the api definition will link only the first registered api.

Installation Environment

The registry of ODM is currently deployed on an Azure virtual machine and it is runnining within a Docker container. Version 0.7 is being used.

Expected Behavior

The referenced link in the api definition should be different for two output ports even if the api object of the promise has the same name and version.

Current Behavior

The api definitions links are all linked to the first registered definition of the port.

Possible Solution

The issue is probably within the IdentityStrategyDefault class within the Parser folder. The parser should provide different references based on the fqdn of the port.

Steps to Reproduce

1. Install 0.7 version of the ODM registry.
2. Call the endpoint to register the base version of the data product descriptor (you can use the attached file):
   http://{{registry_url}}:8001/api/v1/pp/registry/products
3. Call the endpoint to register a new data product version, using as body the attached file:
   http://{{registry_url}}:8001/api/v1/pp/registry/products/{dp-id}/versions
4. Observe the response, and explore the links for the definitions of the promise's apis in the output ports. They have the same FQDN auto-generated, same id and same link. The links are therefore the same for both of the output ports because they have the same name and version, even if the defintion of the apis is different.

Attachments

• Data Product descriptor: dps_openapi.json
• Base Data Product Descriptor: dps_openapi.json