eclipse-tractusx / eclipse-tractusx/traceability-foss
Provide Data Consumption and Data Provisioning over seperated capabilities
- Dominant language
- Java
- Stars
- 17
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
**As** Trace-X
**I want** each capability (Data Provisioning and data Consumption) separated in trace-x architecture
**so that** we have a clear and comprehensible architecture using EDC infrastructure
## Hints / Details
- ...
## Acceptance Criteria
- [ ] Data Provisioning is a configurable capability providing an EDC Provider Instance
- [ ] Data Consumption is a configurable capability providing an EDC Consumer Instance
- [ ] Notifications uses the EDC Consumer of Data Consumption capability
- [ ] Data Provisioning facette could be enabled and disabled via HELM configuration
## Out of Scope
- ...
Contributor guide
Research direction
Start by mapping the existing Trace-X architecture and how it uses EDC Provider and Consumer instances. Inspect the Helm configuration and the Notifications path first; done means configurable, separable Data Provisioning and Data Consumption capabilities, with Notifications using the Data Consumption consumer and Provisioning enablement controlled through Helm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, java
- Domain
- backend, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100