hey guys, if you are using vault as one of the backend repo for spring-cloud-config - It requires the clients to configure a vault token under spring.cloud.config.token and pass the same as a header to the spring-cloud-config-server. But this opens up the token to the world and leak the same.
It's fixed in a snapshot and I was looking to avoid adding a snapshot dependency... Hoping you could tell me if there was some other kind of workaround. I ended up adding the cloud commons snapshot as a dependency but that's obviously not optimal.