EDC version while running. #4471
-
|
Hi everyone, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
nope, such an endpoint does not exist because the EDC version is not relevant at runtime. You can get version information for the DSP API and for all of EDC's REST APIs though. If you talk to another EDC via DSP, you don't care what that connector's runtime version is, because all you care about is that it behaves according to the DataSpace Protocol (DSP). If you want to know the version of your EDC (i.e. that runs in your K8S cluster) then that is a deployment problem, not an EDC problem. |
Beta Was this translation helpful? Give feedback.
-
|
If I run the command: gradle build --INFO I'm able to see traces such as: |
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry, I don't understand your question. If you have a Java project, presumably a Gradle project that uses EDC modules, you have to declare your EDC dependencies somewhere, either in your build file or in a version catalog. So unless you are using version wildcards (in which case your build is bad, and you should feel bad :)), you already know what version you are using, because, well, you put it there...? |
Beta Was this translation helpful? Give feedback.
nope, such an endpoint does not exist because the EDC version is not relevant at runtime. You can get version information for the DSP API and for all of EDC's REST APIs though.
If you talk to another EDC via DSP, you don't care what that connector's runtime version is, because all you care about is that it behaves according to the DataSpace Protocol (DSP).
If you want to know the version of your EDC (i.e. that runs in your K8S cluster) then that is a deployment problem, not an EDC problem.