Note: this guide is still work in progress, if you have some additional feedback to give, please use the related discussion: #1579
So far the SQL datasource configuration was 1:1 with the "store context" one, so the EDC forced to use a dedicated
datasource for every store, now the two concepts are separated, so by default there will be a single default datasource
defined in the Helm Chart and by default all the stores will use that.
So, if you are not using the provided Tractus-X Helm Charts and you don't
need to use different datasources for different stores, we suggest to remove all the edc.datasource.<xxx> settings and
leave just the edc.datasource.default settings group. If you use the Tractus-X EDC Helm Charts there is no further action required on your part.
In any case please follow the advice given by the WARNING log messages in the EDC console output.
Ref. https://eclipse-edc.github.io/documentation/for-contributors/postgres-persistence/
For those who are not using either the Helm Charts or the provided migration modules:
- contract negotiation- create state index
- data plane instance - init schema
- federated catalog - init schema
- policy monitor - create state index
- policy definition - add profiles column
- WARNING: When upgrading from 0.7.X, if your policy definition table already has data, this migration will lead the PolicyDefinitionStore to throw runtime errors. As a workaround you can manually run the query contained in the subsequent migration. The migration fix will be available from 0.8.1 on.
- transfer process - create state index
There were many deprecations deleted after some time, mostly regarding spis, something about configuration settings.
Management API didn't change, we're still using upstream version 3.
If you noticed and took care of everything that was logged as WARNING (which we strongly recommend) you shouldn't find
any other difficulties.
A new extension was added that allows a dataspace participant to prematurely retire an active contract agreement. Once a contract agreement is retired, all existing transfer processes will be terminated. New transfer process requests, using the retired contract agreement, will also fail to start.
The extension adds a set of API endpoints that allow the dataspace participant to manage its retired contract agreements. API details can be found in the OpenAPI specification.
Further details about the extension can be found in the extension README file.
When using the distributed tractusx-edc docker images, you can now specify program arguments that will change how the Connector behaves. Example:
docker run edc-runtime-memory:0.8.0 --no-color
The supported program arguments and their behavior are:
- Removing the coloring option of the default Console Monitor logs by using the program argument
--no-color. - Changing the Connectors' default Console Monitor log levels by using the program argument
--log-level=WARNING. Possible log levels are[SEVERE, WARNING, INFO, DEBUG].
If you use the TractusX helm charts, you can change the log level of the default Console Monitor by changing the
logs.level configuration in values.yml of you chart (example below). The default level is set as DEBUG by default.
tractusx-edc/charts/tractusx-connector-memory/values.yaml
Lines 77 to 79 in 03df535
The old log level configurations were removed (below), as they were not used by the connector in any way and could induce the user of the helm charts in error.
#-- configuration of the [Java Util Logging Facade](https://docs.oracle.com/javase/7/docs/technotes/guides/logging/overview.html)
-logging: |-
-.level=INFO
-org.eclipse.edc.level=ALL
-handlers=java.util.logging.ConsoleHandler
-java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
-java.util.logging.ConsoleHandler.level=ALL
-java.util.logging.SimpleFormatter.format=[%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS] [%4$-7s] %5$s%6$s%n