Misconfig or Bug in DTR?

[arnoweiss]

I have a DTR deployment that is configured like this. It works on the last released docker image, so it's not surprising that the the globalAssetIds don't appear yet in the Discovery-Service. However, I can't see the asset links with specificAssetIds either.

I'm unsure if this is a config or a development issue.

[aaronzi]

Sorry for the late replay here. Since the standalone Discovery works perfectly fine with SpecificAssetIds I would guess that there is a development issue (most probably in the AAS Discovery Integration feature of the AAS Registry)