Azure App Service not recognizing application settings after Terraform deployment
I'm confused about I am currently working with an scenario where my Azure App Service is not recognizing the application settings that I defined in my Terraform script... After successfully running `terraform apply`, I can see that the settings are displayed in the Azure portal, but my application is unable to access these settings during runtime. The behavior message I receive indicates that the configuration values are `undefined`. Here is a snippet of my Terraform configuration: ```hcl resource "azurerm_app_service" "example" { name = "my-app-service" location = azurerm_resource_group.example.location resource_group_name = azurerm_resource_group.example.name app_service_plan_id = azurerm_app_service_plan.example.id app_settings = { "DatabaseConnectionString" = var.db_connection_string "SomeOtherSetting" = var.other_setting } } ``` In my `variables.tf`, I have defined the variables like this: ```hcl variable "db_connection_string" { type = string } variable "other_setting" { type = string } ``` I pass the values for these variables through a `terraform.tfvars` file: ```hcl db_connection_string = "Server=myserver;Database=mydb;User Id=myuser;Password=mypassword;" other_setting = "SomeValue" ``` After deployment, I verified the settings in the Azure portal, and they appear as expected. However, when I run the application, it seems to not be able to access `DatabaseConnectionString`. I have checked the application code and it’s attempting to read the settings using the .NET Core configuration like this: ```csharp var connectionString = Environment.GetEnvironmentVariable("DatabaseConnectionString"); ``` I have also tried to redeploy the app service and explicitly set the settings through the Azure portal, but still no luck. I ensured that the environment variable names match exactly, including case sensitivity. Has anyone encountered a similar scenario or does anyone know what might be going wrong here? Any insights would be greatly appreciated! This is happening in both development and production on Windows 10. Any suggestions would be helpful.