azurerm_windows_web_app - Tomcat version returned is different 10.0 -> 10.0.2

[katbyte]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.x

AzureRM Provider Version

4.5.0

Affected Resource(s)/Data Source(s)

azurerm_windows_web_app

Terraform Configuration Files

erraform {
  required_providers {
    azurerm = {
      source = "hashicorp/azurerm"
      version = "4.5.0"
    }
  }
}

provider "azurerm" {
  features {}
  subscription_id = "REDACTED"
}

resource "azurerm_resource_group" "example" {
  name     = "examplerg-REDACTED"
  location = "West Europe"
}

resource "azurerm_service_plan" "example" {
  name                = "examplesp-REDACTED"
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_resource_group.example.location
  sku_name            = "P1v2"
  os_type             = "Windows"
}

resource "azurerm_windows_web_app" "example" {
  name                = "examplewa-REDACTED"
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_service_plan.example.location
  service_plan_id     = azurerm_service_plan.example.id

  site_config {
    application_stack {
      current_stack = "java"
      java_version = "11"
      tomcat_version = "10.0"
    }
  }
}

### Debug Output/Panic Output

```shell
10.0 -> 10.0.2

The payload sent to Azure as part of the relevant PUT request has a value that is "" for javaContainerVersion, which represents the desired Tomcat version. 

this can be done post initial provisioning via portal.

Expected Behaviour

No response

Actual Behaviour

As of AzureRM 4.5.0, it is not possible to update an azurerm_windows_web_app 's site_config.application_stack.tomcat_version after provisioning.
A reproduction HCL configuration follows.

Steps to Reproduce

No response

Important Factoids

No response

References

No response