v1.11.16

[1.11.16] - 2024-02-20

Added

Changed

• Bug fixes related to Federated Catalogue and Skill Provisioning

Removed

agent-connector-memory-1.11.16

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector using In-Memory Persistence. This is a variant of the Tractus-X In-Memory Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as HashiCorp Vault are included. This chart is intended for use with an existing HashiCorp Vault.

agent-connector-azure-vault-1.11.16

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector configured against Azure Vault. This is a variant of the Tractus-X Azure Vault Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as a PostgreSQL database and Azure KeyVault are included. This chart is intended for use with an existing PostgreSQL database and an existing Azure KeyVault.

agent-connector-1.11.16

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector. This is a variant of the Tractus-X Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as a PostgreSQL database and HashiCorp Vault are included. This chart is intended for use with an existing PostgreSQL database and an existing HashiCorp Vault.

agent-connector-memory-1.11.16-SNAPSHOT

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector using In-Memory Persistence. This is a variant of the Tractus-X In-Memory Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as HashiCorp Vault are included. This chart is intended for use with an existing HashiCorp Vault.

agent-connector-azure-vault-1.11.16-SNAPSHOT

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector configured against Azure Vault. This is a variant of the Tractus-X Azure Vault Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as a PostgreSQL database and Azure KeyVault are included. This chart is intended for use with an existing PostgreSQL database and an existing Azure KeyVault.

agent-connector-1.11.16-SNAPSHOT

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector. This is a variant of the Tractus-X Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as a PostgreSQL database and HashiCorp Vault are included. This chart is intended for use with an existing PostgreSQL database and an existing HashiCorp Vault.

v1.10.15

[1.10.15] - 2023-11-22

Added

• Transfer: Possibility to download skill asset code
• Matchmaking Agent: Update of already registered Skill Assets
• Federated Catalogue: Support multiple offers of same asset
• Auth JWT: allow to exclude certain paths (e.g. liveness)

Changed

• Adapted to Tractus-X EDC 0.5.3 and the new Asset Management v3
• Avoid double checking (allow/deny) of target service urls
• Possibility to run against older EDC versions
• Upgraded to the latest possible version of dependent libraries
• Introduce new
• configuration property compatible with environment variable standards

Removed

• Cyclone DX BOMs (we have Dash)
• Deprecate some configuration property names as not being compatible with environment variable standards

agent-connector-memory-1.10.15

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector using In-Memory Persistence. This is a variant of the Tractus-X In-Memory Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as HashiCorp Vault are included. This chart is intended for use with an existing HashiCorp Vault.

agent-connector-azure-vault-1.10.15

A Helm chart for an Agent-Enabled Tractus-X Eclipse Data Space Connector configured against Azure Vault. This is a variant of the Tractus-X Azure Vault Connector Helm Chart which allows to deal with several data (and agent) planes. The connector deployment consists of at least two runtime consists of a Control Plane and one or several Data Planes. Note that no external dependencies such as a PostgreSQL database and Azure KeyVault are included. This chart is intended for use with an existing PostgreSQL database and an existing Azure KeyVault.