| Platform | Status |
|---|---|
| Windows |  |
| Linux |  |
Install-Package SodaPop.ConfigExplorer
dotnet add package SodaPop.ConfigExplorer
if (env.IsDevelopment)
{
//config is the `IConfigurationRoot` from your `ConfigurationBuilder`
app.UseConfigExplorer(config);
}Once configured, access a diagnostic listing of all the available keys and values in the configuration system via:
http://localhost:port/config
Configuration can often contain application secrets such as connection strings. As a precautionary measure the end point will only load if the host is localhost and we will also filter out any configuration key which has a name containing ConnectionString. Even with these set, we strongly advise this middleware is only added in development environments.
The configuration system in AspNet Core is extremely flexible, but it sometimes can be hard to know what value you're going to receive. An example configuration might look like:
var config = new ConfigurationBuilder()
.AddJsonFile("appsettings.json")
.AddJsonFile($"appsettings.{env.EnvironmentName}.json")
.AddJsonFile("someotherappsetting.json", optional: true)
.AddInMemoryCollection()
.AddEnvironmentVariables()
.Add(MyCustomSource)
.Build();Depending on where you're running, what environment variables are set on the current machine, which configuration options you're using, what order the configuration items are added, which files are present or not present can result in you getting different configuration.
Compounding this, there are a number of "magic" prefixes used to hook in for Azure integration.
This tool will simply list out all the keys and values currently available in the entire configuration system.
app.UseConfigExplorer(config, new ConfigExplorerOptions //optional
{
LocalHostOnly = true, //default
PathMatch = "/config", //default
TryRedactConnectionStrings = true //default
});