Azure Terraform中site_config参数解析及应用服务运行时环境配置疑问

What is site_config? #

The site_config nested block in the azurerm_app_service resource is your go-to for customizing application-level settings beyond basic resource details (like name, location, or app service plan). It’s not just for runtime environments—it controls everything from debugging flags and HTTP protocol versions to CORS policies, performance tweaks, and language-specific runtime configurations.

Is site_config used to specify the Runtime Environment (RTE)? #

Absolutely—this is one of its most practical and common uses. When you set properties like dotnet_framework_version (as in your example) or node_version for Node.js apps, you’re explicitly telling Azure which runtime to use for your application.

For Node.js specifically, if you ran into issues with versions from older discussion threads, that’s likely because Azure regularly retires outdated runtime versions (e.g., Node.js 14 is no longer supported as of mid-2023). Always verify the latest supported versions in the Azure Portal (under your App Service → Configuration → General Settings) before setting this value.

Why is site_config marked as optional? #

Azure App Service has a built-in runtime auto-detection feature. When you deploy your code (via Git, Zip Deploy, or other methods), Azure scans for language-specific files to infer the correct runtime automatically:

• For .NET apps: Checks web.config or project files to determine the framework version
• For Node.js apps: Looks at package.json or entry-point files (like server.js) to pick a compatible Node.js version

If your app follows standard project structures, Azure will configure the runtime without you needing to define site_config. The block is only required when you want to:

• Override the auto-detected runtime (e.g., force using Node.js 20 LTS instead of the default 18)
• Enable/disable features like remote debugging
• Configure advanced settings like CORS, HTTP/2, or local cache

Example: Configuring a Node.js App with site_config #

Here’s a valid Terraform snippet for a Node.js app using a currently supported runtime version:

resource "azurerm_app_service" "node_app" {
  app_service_plan_id = azurerm_app_service_plan.appPlan.id
  location            = azurerm_resource_group.rg.location
  name                = "my-nodejs-app"
  resource_group_name = azurerm_resource_group.rg.name

  site_config {
    node_version = "20-lts" # Use a version listed in Azure Portal's supported runtimes
    http2_enabled = true
    remote_debugging_enabled = false # Disable this in production environments!
  }
}

Other Useful site_config Settings #

Beyond runtime versions, you can use this block to configure a range of other app behaviors:

• .NET Core apps: dotnet_core_version = "6.0"
• CORS policies:

  site_config {
    cors {
      allowed_origins = ["https://your-frontend.com", "https://another-domain.com"]
      support_credentials = true
    }
  }
  

• Performance tweaks: local_cache_enabled = true to enable persistent local storage for your app
• Security: ftps_state = "Disabled" to turn off FTPS access

内容的提问来源于stack exchange，提问作者juztcode