-
Notifications
You must be signed in to change notification settings - Fork 33
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
Periods in ConfigMap keys get replaced by colons without any possibility of escape. #155
Comments
Thanks, good catch! I think this was originally to match K8s |
Well the way the dotnet parses env variables would work. That escapes : with _. So it would be a changing change. |
Maybe we can wind up supporting 3 options (overloads, conceptually) when configuring the configuration provider for a specific ConfigMap:
About the only restriction here is that the resulting keys cannot contain a |
Also worth noting the section in the docs relating to |
Hi - can you give v2.5.7-develop.2 a try and see if that works for you? When setting up your configuration, there is now an additional parameter you can pass ( |
Sorry, that was the wrong branch. Will try again 🙂 |
Ok - can you give v2.5.0-configmap-key-escape.51 a try? |
dotnet-kube-client/src/KubeClient.Extensions.Configuration/ConfigMapConfigurationProvider.cs
Line 133 in 117c4f8
Techincally, Microsoft.Extensions.Configuration, supports key values with periods in their names. For instance, in JSON:
But there's no way to represent this pattern in a ConfigMap.
Perhaps some escaping syntax.
The text was updated successfully, but these errors were encountered: