Cultiv.EnvironmentInspect 2.1.0

Cultiv.EnvironmentInspect ·

v1 is for Umbraco v9 to v13
v2 is for Umbraco v17+

Cultiv Environment Inspector installs a dashboard in the Settings section of Umbraco, showing you the currently applied environment values and where they are coming from.

For example, we can see some of the values here are coming from appsetting.json and from Umbraco Cloud Environment variables.

This makes it easier to learn why some variables you expected to work have not been applied.

Features

• 📊 View all configuration values and their sources in the Umbraco backoffice
• 🔒 Redact sensitive data with multiple redaction modes (Full, Partial, Advanced)
• 🎯 Exclude configuration keys using regex patterns
• 🔐 Provider-based filtering - match by provider type, source file, or full name
• � Copy keys and values with one-click clipboard support and notifications
• ☁️ Azure Web App JSON export - copy configuration as ready-to-use Azure Web App JSON snippets
• 🔄 Environment variable format - convert keys from Umbraco:CMS:Setting to UMBRACO__CMS__SETTING
• �🚀 Performance optimized with runtime caching and change detection
• 🔄 Hot reload support - configuration changes are automatically applied

Installation

Install via NuGet:

dotnet add package Cultiv.EnvironmentInspect

Or via the NuGet Package Manager Console:

Install-Package Cultiv.EnvironmentInspect

Usage

1. Install the package
2. Access the dashboard in Settings → Environment Inspector
3. View all configuration values and their sources

That's it! The package works out of the box with no configuration required.

Dashboard Features

• Copy buttons - One-click clipboard copy for keys and values with success notifications
• Filter options - Toggle to exclude empty values, show only redacted items, or convert keys to environment variable format
• Azure Web App export - Enable AzureWebAppAdvancedCopy to get a ☁️ button that copies Azure-ready JSON snippets
• Virtual scrolling - Efficiently handles thousands of configuration entries

Configuration (Optional)

If you need to exclude or redact sensitive values, add the EnvironmentInspect section to your appsettings.json:

{
  "EnvironmentInspect": {
    "Exclude": [
      "^APPSETTING_",
      "^AZURE_",
      "^EnvironmentInspect",
      "^\\$schema$"
    ],
    "Redact": [
      {
        "Key": "Umbraco:CMS:Unattended:UnattendedUserPassword",
        "RedactionMode": "Advanced",
        "RedactionOptions": {
          "KeepFirst": 2,
          "KeepLast": 2
        }
      },
      {
        "Key": "ConnectionStrings:.*",
        "RedactionMode": "Advanced",
        "RedactionOptions": {
          "Keys": [ "Password", "PWD" ],
          "KeepFirst": 2,
          "KeepLast": 2
        }
      },
      {
        "Key": ".*Password$",
        "RedactionMode": "Full"
      },
      {
        "Key": ".*Secret.*",
        "RedactionMode": "Full"
      },
      {
        "ProviderType": "AzureKeyVaultConfigurationProvider",
        "RedactionMode": "Full"
      }
    ],
    "RedactionCharacter": "•",
    "PartialVisibleChars": 4,
    "AzureWebAppAdvancedCopy": false
  }
}

Results:

• UnattendedUserPassword: 12••••90 🔐
• Connection string password: 7R••••($ (extracted from connection string) 🔐
• Keys matching .*Password$: •••••••• 🔒
• Keys matching .*Secret.*: •••••••• 🔒

For detailed configuration options, see the Configuration Guide.

Umbraco Cloud

For Umbraco Cloud deployments, see the Umbraco Cloud configuration example which includes recommended redaction rules for:

• Azure Blob Storage SAS tokens
• Website authentication keys
• Database connection strings
• Umbraco Forms reCAPTCHA keys

Documentation

• Configuration Guide - Detailed configuration options, examples, and best practices

Best Practices

1. Order matters: Place specific redaction rules before general ones
2. Test regex patterns: Use regex101.com to validate your patterns
3. Use Advanced mode for connection strings: Extract and redact only the sensitive parts

License

MIT License - see LICENSE file for details.