Impact of HashiCorps switch to BSL #233
Replies: 5 comments
-
|
Portal product is not affected (no HashiCorp dependencies) |
Beta Was this translation helpful? Give feedback.
-
|
Knowledge Agents -> Agent Plane Hashicorp Flavour depends on Tractus-X EDC Data Plane Hashicorp Flavour. |
Beta Was this translation helpful? Give feedback.
-
|
puris is affected indirectly. It has a local deployment including the Hashicorp Vault in Version 1.13.3 to spin up EDCs. The application itself does not rely on the vault. |
Beta Was this translation helpful? Give feedback.
-
|
The EDC is using HashiCorp Vault for storing secrets. Therefor it contains a Client implementation: https://github.com/eclipse-edc/Connector/tree/main/extensions/common/vault/vault-hashicorp |
Beta Was this translation helpful? Give feedback.
-
|
Last Thursday the OpenTofu fork made their first release. As this is a drop-in replacement I think we should give it a try. Unfortunately there are no official Docker images yet - but I think this only a matter of days. (PS: As this fork is supported by the Linux Foundation I doubt it will go away anytime soon) |
Beta Was this translation helpful? Give feedback.
-
What happened
On Aug 10, 2023 HashiCorp announced a transition from the Mozilla Public License v2.0 (MPL 2.0) to the Business Source License (BSL, or BUSL) v1.1 for future releases of all products and several libraries.
HashiCorp APIs, SDKs, and almost all other libraries will remain MPL 2.0.
Infos about the Business Source License (BSL, or BUSL) v1.1:
From the HashiCorp FAQ:
The latest releases under MPL are:
Security fixes will be backported under MPL 2.0 through December 31, 2023.
Potential impact on Tractus-X
We have to investigate and need help from the product teams, please provide input:
If you are using one of the tool do NOT upgrade to higher versions as mentioned above!
Beta Was this translation helpful? Give feedback.
All reactions