agent-connector-azure-vault-1.10.3-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.10.3-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.9.8

[1.9.8] - 2023-09-04

Added

• Matchmaking Agent: Possibility to invoke Skills as Services according to KA-MATCH
• Matchmaking Agent: Possibility to steer Delegation through Asset Properties
• Matchmaking Agent: Possibility to allow/deny service requests based on URL pattern
• Transfer: Possibility to annotate assets with service request allow/deny patterns
• Transfer: Implement Skill Protocol of KA-TRANSFER
• Federated Data Catalogue: Embedding Shapes Properties as Named Graphs
• Skill Store: Implementation using EDC Control Plane/Asset Catalogue

Changed

• Adapted all Catena-X namespaces to https://w3id.org/catenax
• Adapted to Tractus-X EDC 0.5 and the changed EDR callback
• Adapted to Tractus-X EDC 0.4 and the v2 Management and Catalogue APIs
• Upgraded to the latest possible version of dependent libraries
• Eclipse Tractus-X standards and migration

Removed

• Previous EDC Control Plane Extensions regarding SPARQL/HTTP transfer

agent-connector-memory-1.9.8

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-memory-1.10.2-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.9.8

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-azure-vault-1.10.2-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.9.8

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-1.10.2-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.

agent-connector-memory-1.9.8-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.