-
Notifications
You must be signed in to change notification settings - Fork 161
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
Configuration properties sections are case sensitive #1296
Comments
I suspect there's something wrong with your app configuration layer, or it executes too late. I'm unable to reproduce this against Steeltoe 3.x. I've tried the following:
Can you provide reproduction steps, so it can be reproduced and debugged? |
i know that it is not an issue with config layer ordering as if I change the casing it correctly resolves it. Would it be helpful if I make a basic repo branch rather than try an describe it? |
I would prefer if you try to reproduce the problem with our sample, gradually adding parts from your app until it breaks. |
Sure thing will do that |
hmm, this is interesting. I have brought across my entire configuration layer and can't reproduce it. Changing the casing still results in it working. Maybe some serialisation behaviour differs? But will need to look into this further. |
Thanks for investigating. I'm closing this, as it doesn't seem to be a Steeltoe issue. Feel free to open a new issue when you've identified what's going on. |
Describe the bug
When i define my app configuration as per https://docs.steeltoe.io/api/v3/discovery/netflix-eureka.html it is not using the values I am supplying via my configuration layer. If i change the sections key to lower case they do correctly resolve.
Steps to reproduce
Steps to reproduce the behavior:
Data.Add("Eureka:Instance:InstanceId", $"192.168.1.1:90");
Data.Add("eureka:instance:InstanceId", $"192.168.1.1:90");
Expected behavior
The configuration parameters are not case sensitive
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: