3.3.2

Fixed

• BPN is now passed on correctly when traversing the item graph
• EDC Policies now get validated regardless of the type of constraint.
• EDC Policies of type FrameworkAgreement are now validated correctly.
• Fixed error in BPN handling for IRS Batch requests

Full Changelog: 3.3.1...3.3.2

irs-helm-6.4.0

IRS Helm chart for Kubernetes

3.3.1

Fixed

• Added missing field businessPartner for relationship aspect SingleLevelUsageAsBuilt

Full Changelog: 3.3.0...3.3.1

irs-helm-6.3.1

IRS Helm chart for Kubernetes

Changed

Update IRS version to 3.3.1

3.3.0

Changed

• BPN is now taken from the submodel data while traversing the item graph
• Tombstone is created if no BPN is available for a child item

Known knowns

• [TRI-1486] IRS does not support businessPartner information for SingleLevelUsageAsBuilt. No trees can be built for direction "upward".
• [TRI-1460] ESS Notifications endpoints are not working in the decentral Digital Twin Registry scenario because endpoints does not provide bpn as a parameter.
• [TRI-1096] No limiting of requests in parallel - IRS allows sending API requests unlimited
• [TRI-1100] Potential denial-of-service (DoS) attack - IRS allows to enter a large number of characters, which are reflected in the response of the server
• [TRI-1098] Software related information disclosure - IRS returns redundant information about the type and version of used software
• [TRI-793] Misconfigured Access-Control-Allow- Origin Header - by intercepting network traffic it could be possible to read and modify any messages that are exchanged with server
• [TRI-1095] HTTP security headers configuration could be improved and allow for additional protection against some web application attacks
• [TRI-1441] Synchronous communication with shared C-X services without circuit breaker pattern - potentially could affect IRS resilience when other services becomes non-responsive.
• [TRI-1441] Cascading effects of failure when Digital Twin Registry becomes non-responsive - potentially bulkhead pattern could improve IRS resilience
• [TRI-1477] Retry mechanism used inside IRS could potentially affect IRS resilience - DDOS other services on which IRS is dependent, exhaustion of resources and available threads, etc.
• [TRI-1478] Lack of resources management - thread pooling, heap limitation etc.
• [TRI-1024] IRS does not support scale out on multiple instances

Full Changelog: 3.2.1...3.3.0

irs-helm-6.3.0

IRS Helm chart for Kubernetes

3.2.1

Fixed

• EDC Policies now get validated regardless of the type of constraint.
• EDC Policies of type FrameworkAgreement are now validated correctly.
• Fixed error in BPN handling for IRS Batch requests

Full Changelog: 3.2.0...3.2.1

irs-helm-6.2.1

IRS Helm chart for Kubernetes

3.2.0

Changed

• The client code for accessing the Digital Twin Registry (central and decentral) is now available as a spring boot maven library. See the README in the irs-registry-client module for more information.
• Update EDC dependencies to 0.1.3
• Add Transformer to support new EDC constraint operator format
• IRS now supports the AAS API 3.0 and its updated models. Note: this also reflects in the Job response shells, please check the new schema.

Known knowns

• [TRI-1460] ESS Notifications endpoints are not working in the decentral Digital Twin Registry scenario because endpoints does not provide bpn as a parameter.
• [TRI-1096] No limiting of requests in parallel - IRS allows sending API requests unlimited
• [TRI-1100] Potential denial-of-service (DoS) attack - IRS allows to enter a large number of characters, which are reflected in the response of the server
• [TRI-1098] Software related information disclosure - IRS returns redundant information about the type and version of used software
• [TRI-793] Misconfigured Access-Control-Allow- Origin Header - by intercepting network traffic it could be possible to read and modify any messages that are exchanged with server
• [TRI-1095] HTTP security headers configuration could be improved and allow for additional protection against some web application attacks
• [TRI-1441] Synchronous communication with shared C-X services without circuit breaker pattern - potentially could affect IRS resilience when other services becomes non-responsive.
• [TRI-1441] Cascading effects of failure when Digital Twin Registry becomes non-responsive - potentially bulkhead pattern could improve IRS resilience
• [TRI-1477] Retry mechanism used inside IRS could potentially affect IRS resilience - DDOS other services on which IRS is dependent, exhaustion of resources and available threads, etc.
• [TRI-1478] Lack of resources management - thread pooling, heap limitation etc.
• [TRI-1024] IRS does not support scale out on multiple instances

Full Changelog: 3.1.0...3.2.0

irs-helm-6.2.0

IRS Helm chart for Kubernetes