[Knowledge Agents] Release Checks

[TomBuchertTSystems]

[!IMPORTANT]
Follow the guidance on how to use the templates.

Release Info

Version to be included in Eclipse Tractus-X release: 1.12.19

Leading product repository: repository link

Compliance Verifications

This issue tracks all checks, that need to be performed for a product release in Eclipse Tractus-X.

• [x] Interoperability checks performed
• [x] Data Sovereignty checks performed

General Checks

• [x] Tractus-X Release Guidelines(TRGs) fulfilled https://github.com/eclipse-tractusx/knowledge-agents/issues/122

[!NOTE] Note: most criteria for documentation and security are now covered in TRGs

Security Checks

• [x] Thread Modelling Analysis passed

Test Results

• [x] E2E Integration Test passed
• [x] User Journey approved

Helpful Links

• Eclipse Tractus-X openAPI specs on SwaggerHub

[TomBuchertTSystems]

@bosserf : Can you please conform user journey?

[TomBuchertTSystems]

Requested appointment for data sovereignty review by @vialkoje

[TomBuchertTSystems]

Requested approval for interoperability by Per-Henrik Addicks

[bosserf]

@TomBuchertTSystems and @kelaja : I herewith give my approval/confirmation regarding the User Journey

[ThomasObermeyer]

@kelaja According to team no interoperability relevant changes for this release, therefore expert approval granted for interoperability

[vialkoje]

Data sovereignty: The business applications have to establish the control plane before accessing the knowledge agents as the dataplane implementation. therefore all topics regarding usage of BPN-L, policy definitions, company-rules and so forth have to be done by the application itself before accessing the knowledge agent API. All relevant QG-criteria are therefore not relevant for this implementation as it only acts as a different way of organizing and transferring the data - that uses an access token provided by the DSP-Sovereign data exchange protocol. Expert approval granted

[almadigabor]

Hey, I've created the TRG check issue. I will need a volunteer committer who does the checks alongside with me. Can you please find me someone? Thanks!

[cbrugg]

INT Tests done. E2E Tests planned to finish today. Data Sov not relevant. Lets discuss in the QG.

[RolaH1t]

QG review 17-May Thread modelling in progress / architecture improved, no major changes TRG checks completely open, based on final version (PR in progress) Test completion expected 17-May final version => 1.12.19 no follow-up mtg required

[szymonkowalczykzf]

Threat Modeling - approved - all previous finding addressed - no major changes to the architecture / new components added.

[cbrugg]

E2E Tests also successfully done. Testmanagement approval is hereby given! Thank you for your efforts!

[RolaH1t]

Hi @almadigabor we trust you are processing the TRG checks on this product. As this is the only topic missing, I can approved the QG fully once completed. Thx Roland

[almadigabor]

Hey @RolaH1t, as we were waiting for the Eclipse IP check issues to be processed this got a bit delayed. Now we managed to merge the last PRs, create the releases and now I can proceed with the checks.

[almadigabor]

I'm done with the first round of checks. There is one issues open regarding critical security findings in the knowledge-agents repository by CodeQL. https://github.com/eclipse-tractusx/knowledge-agents/issues/128

Once they are addressed, I can approve and close the TRG checks issue.

[almadigabor]

As the security findings were false positives as they've already been fixed, the last check is also marked. I approve the QG with the following versions:

App version: 1.12.19 Chart version: 1.12.19

[RolaH1t]

Congrats: Quality Gate fully approved with all necessary pre-requisites fulfilled! Thanks for all your efforts, Roland

[FaGru3n]

Hi @RolaH1t and @kelaja guess could be closed, many thanks for your work.

[stephanbcbauer]

Hello @TomBuchertTSystems

Since the feature is a 24.05 feature and the development phase for 24.08 is coming to an end, we need a status on the feature. Can you please update the status?

• [ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• [ ] Please check whether the status (backlog, work in progress ...) is set correctly
• [ ] Please comment on the current status of the feature
• [ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.
• [ ] Is there a spillover planned?

If you need any clarification, please get in touch, thank you very much.

Stephan