Skip to content

Support for a YAML configuration provider #1904

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

Closed
tomkerkhove opened this issue Jul 1, 2019 · 9 comments
Closed

Support for a YAML configuration provider #1904

tomkerkhove opened this issue Jul 1, 2019 · 9 comments

Comments

@tomkerkhove
Copy link
Member

In container land, YAML is used in favor of JSON which is not supported in .NET Core OOTB. Would be good to have a YAML configuration provider.

This is already available via https://github.com/andrewlock/NetEscapades.Configuration but would be good to have official support for this OOTB.

@hishamco
Copy link
Member

hishamco commented Jul 3, 2019

If I'm not wrong this issue is already logged from 1.0, but it closed, coz there's no plan to support it

@tomkerkhove
Copy link
Member Author

Thanks for the update @hishamco but 1.0 is a long time ago, time to see if we can revise that decision!

@ichensky
Copy link

ichensky commented Jul 5, 2019

@davidfowl
Copy link
Member

This is already available via https://github.com/andrewlock/NetEscapades.Configuration but would be good to have official support for this OOTB.

Why should it be in the box?

@tomkerkhove
Copy link
Member Author

Because YAML is used more and more + .NET is always mentioned to be a good candidate for microservices.

However, microservices are often shipped via containers wherein the container space YAML is used for configuration over JSON.

@davidfowl
Copy link
Member

We're not going to change the default from JSON to Yaml, I'd suggest using the above library if you want yaml based configuration files.

@tomkerkhove
Copy link
Member Author

I'm not saying that it should be the new default, I'm just wondering why YAML is not supported OOTB.

Anyhow, I could only ask.

@davidfowl
Copy link
Member

Several reasons:

  • It requires a dependency on a Yaml parser.
  • It wasn't deemed important to ship OOTB by the team.
  • There are various 3rd party implementations that do a good job.

@tomkerkhove
Copy link
Member Author

A pity but fair enough

@ghost ghost locked as resolved and limited conversation to collaborators Dec 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants