Persistent submodel service needed for end-to-end stability #1459
Description
As a developer or system integrator,
I want a Submodel Service that persists submodel data in a database,
so that data is not lost after service restarts and the IRS-to-Trace-X process can function end-to-end reliably.
Hints / Details
- Currently, submodel data is lost after each restart of the Submodel Service.
- During IRS E2E tests, this results in missing submodel data at the end of the process.
- The process technically completes, but cannot forward the submodel to Trace-X.
- This restricts the functionality of both Trace-X and IRS.
- The continuous need to re-provision submodels after each restart is inefficient and time-consuming.
Acceptance Criteria
- Submodel data is stored persistently in a database.
- After a service restart, previously created submodels are still available.
- IRS can successfully forward submodels to Trace-X without manual re-provisioning.
- Manual provisioning after each restart is no longer necessary.
Out of Scope
- Changes to the IRS or Trace-X logic beyond submodel availability.
- Migration of legacy or test data.