Extensions: Refactor things so data format of the provider is not tied to File based providers

Created on 16 May 2017  路  5Comments  路  Source: dotnet/extensions

For example, JSON/XML format with streams.

3 - Done area-config enhancement

Most helpful comment

I would also like to see the JsonConfigurationFileParser made public. I am launching subprocesses and use anonymous pipes to push a json configuration document to the child process for configuration. I would like to be able to use the parser to take the stream from the pipe and turn it into config that I can then use with the configuration lib. Right now, I've simply taken a copy of your parser into my project; it would feel less dirty just calling in from the package.

All 5 comments

We want to retrieve some secrets from a vault of some sort and replace parts of the configuration with these secrets. Making the JsonConfigurationFileParser public and adding the stream support would really help with this. What's the status on this work?

Moved here from config repo. See old PR: https://github.com/aspnet/Configuration/pull/822

I would also like to see the JsonConfigurationFileParser made public. I am launching subprocesses and use anonymous pipes to push a json configuration document to the child process for configuration. I would like to be able to use the parser to take the stream from the pipe and turn it into config that I can then use with the configuration lib. Right now, I've simply taken a copy of your parser into my project; it would feel less dirty just calling in from the package.

Adding my +1 so that we can use the parsing for things like getting config from an embedded resource in an assembly (A scenario that come up last week for me).

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JunTaoLuo picture JunTaoLuo  路  4Comments

pengweiqhca picture pengweiqhca  路  7Comments

shirhatti picture shirhatti  路  6Comments

halter73 picture halter73  路  6Comments

grahamehorner picture grahamehorner  路  3Comments