Closed saudkhan116 closed 10 months ago
@saudkhan116 I was not able to reproduce the issue. I registered a Shell without SerialPart submodel descriptor in DTR service, and then started a Job in IRS, and it collected relationships successfully. Can you check one more time and potentially provide some more details?
Hints
- One possible Solution: API Refactoring - change the default value for aspect types to an empty list.
- Expected Behaviour with an empty aspect types list:
- if the array of aspect types is empty --> no aspect models will be collected and the process will run only on the relationTypeAspects
Acceptance Criteria
- [ ] aspects Schema in the API documentation has been refactored
- [x] A tavern or cucumber test has been created for this behaviour to tested
- [ ] Behaviour has been verfied
- [ ] Bug is fixed
- [ ] Bug is mitigated and documented in Github
Tavern test has been adjusted and check methods added for expected behaviour:
Changes are pushed to branch "feature/TRI-1658-infected-supply-chain-on-first-tier-level"
Default behavour changes, PR merged: https://github.com/catenax-ng/tx-item-relationship-service/pull/655
@saudkhan116 I was not able to reproduce the issue. I registered a Shell without SerialPart submodel descriptor in DTR service, and then started a Job in IRS, and it collected relationships successfully. Can you check one more time and potentially provide some more details?
Hi @ds-ext-kmassalski, Thank you for your reply. Unfortunately, I could not execute the IRS job to reproduce this issue and provide you more details at the moment. I get "ACCESS DENIED", I think this is the problem of authentication with the MIW on INT.
@saudkhan116 since MIW is resolved, could you reproduce this behaviour?
we implemented this.
@saudkhan116 since MIW is resolved, could you reproduce this behaviour?
Hi @jzbmw, IRS doesn't work because of the keycloak configuration changes in version 4.1.0 (from the centrally managed keycloak in Portal), unfortunately we cannot reproduce the issue as long as the IRS works again.
Everything works as expected, thanks 👍
Introduction
We found an issue while utilizing the IRS-API component. We didn't register the SerialPart aspect model and we get empty relationships in the IRS job response. When we define the SeirialPart submodel, we are able to retreive the relationships and submodelDescriptors.
Problem Description
Job Request
Job Response
Here is the response payload of the IRS Job which does not contain relationships and submodelDescriptors. In the original digital twin, there is battery digital product passport and BOMasBuilt aspect models but not a SerialPart aspect defined.
Working Solution
When the SerialPart aspect was included in a digital twin, the IRS retrieves asuccessful payload with relationships and submodelDescriptors:
I hope this helps. If you need anything please let me know.
Thank you!
Kind Regards, DPP Team