REST endpoints for related resources are ambiguous

[dvob]

The REST endpoints to edit properties of resource relations are ambiguous. If you add the same resource to an application server twice its no longer possible to specify which resource relation you want to edit. This leads to a couple of strange behaviour on different REST endpoints:

• GET /resources/{resourceGroupName}/{releaseName}/relations/{relatedResourceGroupName}/{relatedReleaseName}/properties: you see each property multiple times but its not clear to which resource relation they belong
• GET /resources/{resourceGroupName}/{releaseName}/relations/{relatedResourceGroupName}/{relatedReleaseName}/properties/{propertyName}: returns randomly one value of all resource relations
• PUT /resources/{resourceGroupName}/{releaseName}/relations/{relatedResourceGroupName}/{relatedReleaseName}/properties/{propertyName}: throws javax.persistence.NonUniqueResultException

Liima Version: 1.16.1
Steps to reproduce:

1. create resource type myResource
2. add a new resource type property myProperty
3. create resource myResource1
4. add myResource1 at least twice to an application server (Add Relation)

The resource should then be shown as myResource1 and myResource1 (myResource1_1) on the application server. Then you can perform the REST calls described above.

[dvob]

Another problem I just found in the web gui: If you remove the relation myResource1 from the application server all the other relations (myResource (myResource1_*)) are removed as well.

[RetGal]

@dsbrng25b Concerning the issue in the web gui: this has been fixed in 1.7.1.
To address the reported issues of the REST endpoints would require a change in the structure of the returned values.