Closed buyukim closed 3 years ago
Okay, looks like I need to manually bump up spring-vault-core from 2.3.0 to 2.3.2
Using Spring Vault 2.3.2 solves the issue. We added additional API to support cipher suites/protocols configuration. I'm not sure what component pulls in an older Spring Vault version. As per Spring Cloud Vault, we refer to the correct version:
d'oh, looks like one of our internal shared libraries is somehow forcing the downgrade. sorry about that. closing
Thanks a lot for the update.
Hi,
I just ran into the same issue, and it turns out the spring-cloud-config-dependencies
BOM (version 3.0.3) defines the version of the spring-vault-core as 2.3.0.
That BOM is imported in the spring-cloud-dependencies
BOM (version 2020.0.2) before the spring-cloud-vault-dependencies
BOM (version 3.0.2), and seems to take precedence.
Is this worth reporting in the spring cloud config repository, or at the spring cloud dependencies level ?
Edit: I just found out it was already tackled in spring-cloud/spring-cloud-config#1841
Getting what appears to be a class loading issue when using the latest spring cloud + boot + spring-cloud-starter-vault-config versions:
Spring Cloud: 2020.0.2 Spring Boot: 2.4.4 Gradle config for vault (org.springframework.cloud:spring-cloud-vault-config:3.0.2 right now):
runtimeOnly 'org.springframework.cloud:spring-cloud-starter-vault-config'
I cannot provide our application, unfortunately. I am confused as to why this constructor is being called, since I am unable to find a version of org.springframework.vault.support.SslConfiguration that has this constructor.