[PRIO 2] Local development setup

[ds-ashanmugavel]

As a contributor
I want to start backend and frontend locally
so that I can participate on the development on trace-x on local resources

Link

• Is blocked by Refactoring notification flow EDC provider #728

Hints / Details

• As a reference, should already be implemented by cofinity: https://github.com/Cofinity-X/cofinity-x-ba-traceability-foss

Acceptance Criteria

• HELM Chart realization to be reused
• Backend can be started locally
• Frontend can be started locally
• Required shared services like (irs, dtr, semantic hub,edc) could be used in local setup (mocks or instances)
• Frontend can use local deployed backend
• External services connected to the backend will be returning mock responses
• Authentication against the portal is not necessary
  • All roles (admin, user, supervisor) MUST be used
• Local deployment is documented in a sufficient way for external contributors
• Upload test data
• Document how to set up (updated)
  • Define what is out of scope and working
  • INSTALL.md

Out of Scope

• Notification flow up and running
• IRS Sync up and working

[ds-ext-sceronik]

@mkanal @jzbmw @ds-mwesener
for local deployment if We should first consider reducing number of used EDCs from 2 to 1 to use only one instance of EDC for consuming and providing purpouses.

Also question if local setup should be single instance or 2 instances deployed and configured that way so it would be possible to send notifications between them ?

[ds-mwesener]

To be discussed.

[mauantoniojw]

in case is helpful, a wiremock image can be useful to mock external services like irs, edcs, etc.
keycloak is something the local environment can also run for auth (realm file that includes Supervisor, User and Admin)

[mkanal]

We have resolved the discussion by adding story #728 which corrects the edc notification flow. Discussion label was removed.

[ds-lcapellino]

Also update the INSTALL.md file in order to have an up to date tutorial.

[ds-lcapellino]

As discussed in today's daily, we moved this issue to the current sprint.

[ds-jhartmann]

Created a configuration for trace-x in the umbrella repository: https://github.com/eclipse-tractusx/tractus-x-umbrella/tree/chore/trace-x-integration
Added frontend configs and documentation how to use the umbrella chart in #1268

• HELM Chart realization to be reused
• Backend can be started locally (as part of umbrella chart)
• Frontend can be started locally
• Required shared services like (irs, dtr, semantic hub,edc) could be used in local setup (mocks or instances)
• Frontend can use local deployed backend (backend as part of umbrella chart)
• External services connected to the backend will be returning mock responses
• Authentication against the portal is not necessary
  • All roles (admin, user, supervisor) MUST be used
• Local deployment is documented in a sufficient way for external contributors
• Upload test data
• Document how to set up (updated)
  • Define what is out of scope and working
  • INSTALL.md

[ds-mwesener]

Story is done. Please validate or move to done. Thanks