-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vault configuration in composite profile is not picked up. #2592
Comments
I could have swore there was an issue around this already...but I can't seem to find it. I seem to remember looking into something similar a while back and discovering that Vault wasn't supported by composite environment repositories (or some properties in the configuration were not supported). I can't seem to find the issue though. |
Probably need to debug here to start Line 51 in 4841d80
Let me know if you have time to take a look. If not I will put it on my list |
@ryanjbaxter I'll take a look and try to find a fix. |
Describe the bug
Any
vault
configuration incomposite
profile is ignored and instead default values are used.Given following configuration for config-server:
When executing
curl -H "X-Config-Token: token" localhost:8888/cook/default
config-server should call vault athttp://my-vault-server:5555
but instead it callshttp://127.0.0.1:8200
.Sample log
NOTE: the behaviour is correct when using
vault
profile, instead ofcomposite
.The text was updated successfully, but these errors were encountered: