{"action":"created","issue":{"url":"https://api.github.com/repos/aspnet/Hosting/issues/346","labels_url":"https://api.github.com/repos/aspnet/Hosting/issues/346/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/Hosting/issues/346/comments","events_url":"https://api.github.com/repos/aspnet/Hosting/issues/346/events","html_url":"https://github.com/aspnet/Hosting/issues/346","id":105431208,"number":346,"title":"Ensure Configuration Provider Used for Hosting Configuration","user":{"login":"Michael-DST","id":2931376,"avatar_url":"https://avatars.githubusercontent.com/u/2931376?v=3","gravatar_id":"","url":"https://api.github.com/users/Michael-DST","html_url":"https://github.com/Michael-DST","followers_url":"https://api.github.com/users/Michael-DST/followers","following_url":"https://api.github.com/users/Michael-DST/following{/other_user}","gists_url":"https://api.github.com/users/Michael-DST/gists{/gist_id}","starred_url":"https://api.github.com/users/Michael-DST/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Michael-DST/subscriptions","organizations_url":"https://api.github.com/users/Michael-DST/orgs","repos_url":"https://api.github.com/users/Michael-DST/repos","events_url":"https://api.github.com/users/Michael-DST/events{/privacy}","received_events_url":"https://api.github.com/users/Michael-DST/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-09-08T17:28:25Z","updated_at":"2015-09-12T22:51:23Z","closed_at":"2015-09-08T17:38:13Z","body":"This is related to issue #269.  A great effort was made to make the Hosting Configuration File in a consistent/expected file format of .json, but the underlying issue was not fully addressed: As discussed in [another issue in Tooling](https://github.com/aspnet/Tooling/issues/140), users (and teams) enjoy and prefer their own data formats when describing objects used for configuration.  Ideally, the Hosting application will leverage the [configuration provider API](https://github.com/aspnet/Configuration) already available with ASP.NET to make it as consistent (and friendly) as the features already available.\r\n\r\nObviously, Json provider will be default, but others will providers can and should be used as well.  Yay for options. :smile: "},"comment":{"url":"https://api.github.com/repos/aspnet/Hosting/issues/comments/139826259","html_url":"https://github.com/aspnet/Hosting/issues/346#issuecomment-139826259","issue_url":"https://api.github.com/repos/aspnet/Hosting/issues/346","id":139826259,"user":{"login":"Michael-DST","id":2931376,"avatar_url":"https://avatars.githubusercontent.com/u/2931376?v=3","gravatar_id":"","url":"https://api.github.com/users/Michael-DST","html_url":"https://github.com/Michael-DST","followers_url":"https://api.github.com/users/Michael-DST/followers","following_url":"https://api.github.com/users/Michael-DST/following{/other_user}","gists_url":"https://api.github.com/users/Michael-DST/gists{/gist_id}","starred_url":"https://api.github.com/users/Michael-DST/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Michael-DST/subscriptions","organizations_url":"https://api.github.com/users/Michael-DST/orgs","repos_url":"https://api.github.com/users/Michael-DST/repos","events_url":"https://api.github.com/users/Michael-DST/events{/privacy}","received_events_url":"https://api.github.com/users/Michael-DST/received_events","type":"User","site_admin":false},"created_at":"2015-09-12T22:51:23Z","updated_at":"2015-09-12T22:51:23Z","body":"Well, I didn't get any additional answers to my question here, but I will say that it feels a little disorganized (and best) and maybe a little spiteful (at worst) to have one team member suggest opening an issue and then another to close it immediately without any meaningful discussion around it first.  I realize everyone is busy, but please do know that my intent here is to ensure great (cross-)use of your codebase and also the valuable guidance that this provides consumers of this code.\r\n\r\nAdditionally, I would also like to make the case that even though this feature is not in the current plans, this issue should remain open in case someone feels so inspired to create a PR around it, as well.  It could happen (that's what all this new-fangled opensourcery is all about, right?). :)  I also realize that keeping the backlog tidy is a value and a priority, and again I would point to at least making this a future feature for consideration instead of straight-up closing without any discussion around it.\r\n\r\nAs always, please feel free to correct me where I am wrong in my thinking here.  I am pretty much a newb around how all this works with all the sourcerers (new word, you're welcome) around here, but it is still a perspective and thought I would share how I see (and feel) it.\r\n\r\nThank you for any consideration (and feedback)."}}