Skip to content

v1.0.0
Compare
Choose a tag to compare
@matbmoser matbmoser released this 16 Aug 18:37
· 1569 commits to main since this release
v1.0.0
024653d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

[1.0.0] - 15-08-2023

What is new?

Added

  • Added new structure to communicate with:
    • EDC discovery
    • Discovery Finder
    • BPN Discovery
    • New digital twin registry decentralized version
    • Integration of AAS 3.0 APIs
  • Added new /create API to start a new process
  • Added BPN number checks on startup to verify
    • Added a check if the EDC Consumer Connector is accesible
    • Added a check if the EDC Connector BPN is the same as the Backend BPN
    • Added a check if the technical user configured is valid
    • Added a check if the technical user configured has the same BPN number as the EDC consumer
  • Added EDC v0.5.0 support
    • Added new models related with the EDC v0.5.0 upgrade
    • Added backend compatibility with EDC v0.4.1
  • Added persistent storage to store contract negotiation details for the data sovereignty
  • Added the mechanism to split the Id into 3 parts CX:<manufacturerPartId>:<serializedId> and check the validity of the Id used
  • Added support for the following Contribution guidelines (TRG) requirements:
    • TRG-1.02: Added instructions to the install.md to set up and install the application
    • TRG-4.02: Added base images information to the main README.md file
    • TRG-4.03: Added user and file permissions to run as a non root user
    • TRG-4.06: Added contents for notice for docker images
    • TRG-5.01: Added helm chart requirements, remove hostnames from the ingress and environment-specific values
    • TRG-5.04: Added resource management settings to limit CPU and memory utilization
    • TRG-5.08: Added comments in the helm values.yaml file
    • TRG-5.09: Added helm-test workflow to verify that a released helm chart works as expected
    • TRG-5.10: Added support of various Kubernetes versions particularly v1.27, v1.26, v1.25 and v1.24 for helm tests
    • TRG-5.11: Added helm-upgrade workflow to achieve pre-release upgradeability of the helm charts
    • TRG Compliance: Complied with all the TRGs: #108

Updated

  • Updated frontend helm charts templates for fixing severe merge configuration bug
  • Updated the models to match the new Digital Twin Registry exchange
  • Optimized the processing time by adding temporary configurable processing storage
  • Updated README.md file of the digital product pass components
  • Updated pom.xml resources configuration
  • Updated ingress annotation to support various Kubernetes versions for helm tests
  • Updated the EDC v0.5.0 configuration
    • Updated SSI configuration in the EDC helm charts
    • Updated Passport storage and how the contract Id key is obtained from the EDR.
    • Updated transfer models
    • Updated helm chart configuration to match the EDC version v0.5.0
  • Updated the DPP postman collection to test the registry APIs in decentralized fashion
  • Updated CONTRIBUTING.md readme file
  • Updated .helmignore to ignore environment-specific values files
  • Updated Chart.yaml by adding new variables home and sources
  • Updated the Backend.js service to call the /create backend api, with the manufacturerPartId, before the actual search
  • Updated DPP documentation to align with current implemention:
    • GETTING-STARTED.md
    • SECRETS_MANAGEMENT.md
    • Arc42.md
    • Admin_Guide.md
    • deployment/readme
    • Fix navigation links in root readme
    • User Manual Product Viewer App.md
    • Consumer-backend readme

Issues Fixed

  • Fixed pom.xml resources and logging configurations to resolve the security vulnerability
  • Fixed indentation issue in a helm default values.yaml
  • Fixed helm testing
  • Fixed application deployment for TRG 5.01

Security Issues

  • Updated the sprint boot version from 3.1.0 to 3.1.2 to fix a high security vulnerability

Known Knowns

Decision on accessibility on Battery Passports

The Regulation (EU) 2023/1542 of the European Parliament [1] requires a battery passport (see Chapter IX, Article 77) issued by the economy operator of a battery. Explicitly, the EU requires this information on a Battery to “be accessible through the QR code” (Article 77, 3) and: “The battery passport should provide the public with information about batteries placed on the market and their sustainability requirements” (123).

In the Battery Pass Viewer App, we follow this regulation. “Public” availability for us is “Catena-X” public, after being successfully logged in to the network. An additional check to match logged in user with the BPN of the utilized EDC is in investigation, to allow potential non-Battery-Passport use cases to further restrict the accessibility of passports in future or custom adoptions of this software.

Therefore, this application in its current release must not be used for any other purpose, especially any other digital product passes than required by (EU) 2023/1542.

[1] https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2023.191.01.0001.01.ENG&toc=OJ%3AL%3A2023%3A191%3ATOC

Full Changelog: v1.0.0-alpha...v1.0.0

Assets 2
Loading