Issue: integrating aws vault and aws s3 config server. exception: The bean 'configTokenProvider', defined in class path resource [org/springframework/cloud/config/server/config/VaultConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [org/springframework/cloud/config/server/config/EnvironmentRepositoryConfiguration$DefaultConfigTokenProvider.class] and overriding is disabled.
Comment From: ryanjbaxter
Can you provide a complete, minimal, verifiable sample that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip file.
Comment From: jaganm2018
It’s working now with integration of vault and config-server with below dependencies. Here is my changes .. 1. Spring cloud dependency: 2020.0.2 2. Added spring cloud config and vault dependencies. 3. Bootstrap file with config server aws s3 and cloud config server vault and cloud vault. my concern: in that bootstrap , I added vault configuration in both spring cloud vault and spring cloud config server vault also. Is there any way we can skip spring cloud config server vault configuration..
please check and suggest me. Added screenshot of bootstrap and dependencies along with this message.
Appreciate your help and responding.
Comment From: jaganm2018
Image not available
Comment From: jaganm2018
Image not available
Comment From: ryanjbaxter
https://github.com/spring-cloud/spring-cloud-config/issues/1921#issuecomment-872442734
Comment From: jaganm2018
I shared the dependencies and my sample bootstrap yml. Please let me know if above information is not sufficient to answer my question, will create sample and provide to you. Thanks a lot.
Comment From: ryanjbaxter
Yes please create a sample in either a Git repo or attach it as a zip as my comment above stated
Comment From: spring-cloud-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-cloud-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.