Built-in configuration providers can do more robust key handling

[maryamariyan]

Found two key handling issues:

cc: @safern

---

Work Items

• ConfigurationBuilder - Configuration.Json: Binding a Dictionary<string,string> error when Key contains an string url like http://www.google.es #42643 Json Configuration Provider - Handling of keys with ":"
• [Feature Request] Add a replacement for dot in EnvironmentVariablesConfigurationProvider #35989 Environment Variable Configuration Provider - Handling of keys with "."
• [API Proposal]: Allow keys with colons in config #67616

[ghost]

Tagging subscribers to this area: @maryamariyan
See info in area-owners.md if you want to be subscribed.

---

Issue meta data

Issue content:	Found two key handling issues: ConfigurationBuilder - Configuration.Json: Binding a Dictionary<string,string> error when Key contains an string url like http://www.google.es #42643 Json Configuration Provider - Handling of keys with ":" [Feature Request] Add a replacement for dot in EnvironmentVariablesConfigurationProvider #35989 Environment Variable Configuration Provider - Handling of keys with "." cc: @safern
Issue author:	maryamariyan
Assignees:	-
Milestone:	-

[NinoFloris]

Particularly #35989 would be a wonderful fix for 6.0.

It's a major hindrance that most logging (beyond first namespace level) cannot be configured ad-hoc once a unix container has been built. (without mucking about with tools like confd or manual fix-ups inside the app)

The feature to change log levels (and other keys) via env vars is really nice and cloud native, it just falls short in polish of the last 5%.

[eerhardt]

We will consider this in a future release. Moving this issue out of the 7.0 milestone.

[SteveDunn]

Hi,
I've got a bit of spare time again, so I'm happy to continue with any of these if they're planned for .NET 9? The 'allow keys with colons' was a biggies as I remember.