spring-cloud / spring-cloud/spring-cloud-vault
not working with new versions
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 291
- Forks
- 152
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 3
Description
Hi,
for a code/repo example I can provide this blog post:
https://medium.com/@zeeshanalamkhan/integrating-hashicorp-vault-with-spring-boot-2-x-7a1be1365d8b
I tried to use example from https://docs.spring.io/spring-cloud-vault/docs/current/reference/html/#quick-start but I see it uses 2.4.0.RELASE which does not exists in mvnrepository.
in short it works fine with older versions of spring-boot-starter-parent ie: 2.13.2.RELASE but not for 2.6.4,
( also there is upgrade needed for spring-cloud 2021.0.1 otherwise we have errors: Caused by: java.lang.NoClassDefFoundError: org/springframework/boot/context/properties/ConfigurationBeanFactoryMetadata )
but well in short, 2.13.2.RELASE -> 2.6.4 and Hoxton.SR12< -> 2021.0.1, no code, config changes at all, just upgraded libs. And I get nulls instead of real values.
Not sure if its a bug, maybe there is needed some other change in code/config.
If you could help me, please.
thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Spring Cloud Vault quick-start documentation and reproduce the reported upgrade from Spring Boot 2.13.2.RELASE to 2.6.4 and Hoxton.SR12 to 2021.0.1. Compare the dependency versions and configuration used in the report, then verify whether the NoClassDefFoundError and null values still occur. Done means the documented setup works with the newer versions or the required compatibility changes are clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100