You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Spring Cloud Config Server(pom: spring-cloud-config-server) up and running and loading all configured properties from the local repo. I also created a new spring cloud config client(pom: spring-cloud-starter-config). I'm using spring-cloud-starter-vault-config to read secrets from the hashicorp vault. Without using any of the above pom references on my standalone project, I'm able to successfully read the contents of hashicorp vault. But if I start using this server/client model, the client is able to retrieve properties from the config server but not from the configured vault. Any help is appreciated.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
I have a Spring Cloud Config Server(pom: spring-cloud-config-server) up and running and loading all configured properties from the local repo. I also created a new spring cloud config client(pom: spring-cloud-starter-config). I'm using spring-cloud-starter-vault-config to read secrets from the hashicorp vault. Without using any of the above pom references on my standalone project, I'm able to successfully read the contents of hashicorp vault. But if I start using this server/client model, the client is able to retrieve properties from the config server but not from the configured vault. Any help is appreciated.
The text was updated successfully, but these errors were encountered: